Group items tagged

Step 2 securing some content

create a database that will hold the list of the authorized users along with their password

Create a new directory “auth” and add a new JSP under it, let’s call it “BackOffice.jsp“

enable Shiro into our project by adding a ServletFilter into our Web.xml

 <filter-class>05            org.apache.shiro.web.servlet.IniShiroFilter06        </filter-class>

10    <filter-mapping>11         <filter-name>ShiroFilter</filter-name>12         <url-pattern>/*</url-pattern>13    </filter-mapping>

classpath:shiro.ini

shiro-core

shiro-web

create shiro.ini under resource dir

07ds.jdbcUrl=jdbc:derby://localhost:1527/shiro_schema08ds.username = APP09ds.password = APP

15/auth/** = authcBasic16/** = anon

jdbcRealm.authenticationQuery

jdbcRealm=org.apache.shiro.realm.jdbc.JdbcRealm

setup the jdbc realm, this is where Shiro will find the authorized users

map the URLs to be protected, all the url under /auth should be authenticated with basic HTTP authentication

All the other URLs should be accessed without authentication

Add a new directory under src let’s call it production we will create a new shiro configuration file compatible with MySQL

06ds.serverName = localhost07ds.user = ADM08ds.password = secret12309ds.databaseName = shiro_schema

jdbcRealm which use a MySQL driver

added the appropriate dependency to maven pom.xml

mysql-connector-java

environment.type

staging

13                <jdbc.user>APP</jdbc.user>14                <jdbc.passwd>APP</jdbc.passwd>15                <jdbc.url>jdbc:derby://localhost:1527/shiro_schema</jdbc.url>16                <jdbc.driver>org.apache.derby.jdbc.ClientDriver</jdbc.driver>

src/main/resources

derbyclient

production

environment.type

45                <jdbc.user>ADM</jdbc.user>46                <jdbc.passwd>secret123</jdbc.passwd>47                <jdbc.ds>com.mysql.jdbc.jdbc2.optional.MysqlDataSource</jdbc.ds>48                <jdbc.serverName>localhost</jdbc.serverName>49                <jdbc.databaseName>shiro_schema</jdbc.databaseName>

src/production/resources

To build and run for staging

To build for production

-Denvironment.type=prod

file listed under the filename parameter can be deployed to the server using the deploy goal

deploy

redeploy

undeploy

<phase>install</phase>

<goal>deploy</goal>

Deploying other artifacts

possible to deploy other artifacts that are not related to your deployment, e.g. database drivers:

<phase>install</phase>

<goal>deploy-artifact</goal>

<configuration> <groupId>postgresql</groupId> <artifactId>postgresql</artifactId> <name>postgresql.jar</name> </configuration>

artifact must be already listed as a dependency in the projects pom.xml.

Deploying your application in domain mode.

add the domain tag as well as specify at least one server group.

<domain> <server-groups> <server-group>main-server-group</server-group> </server-groups> </domain>

If the JPA entities still do not look right, try to apply some JPA tricks like mapping a JPA-entity to several tables, or even map JPA-entities to DB-views, to improve the situation

Rename the classes into some more meaningful. The attribute, class names are in general everything but not fluent

Junit. Purpose: JPA mapping verification

Thinking In Structs Not Objects

12 Tips On JPA Domain Modelling

Execute the "Unit" tests after every change

even better get rid of them

domain objects are

right-clicking the test class in the IDE and selecting Run As > * Test

summary of templates used by the generator depending on the kind of Java class it encounters:

these templates are bundled in the granite-generator.jar archive, in the org.granite.generator.template package and accessible as resources via the class loader

class: protocol is used because all standard templates are available in the classpath

Alternatively, you may use the file: protocol to load your template from the filesystem. These templates can be specified either by using absolute paths (eg. file:/absolute/path/to/mytemplate.gsp) or paths relative to your current Eclipse project root directory (eg. path/to/mytemplate.gsp).

ActionScript 3 generator is able to write AS3 typed client proxies for exposed remote services

Compared to the usual Flex RemoteObject, this can greatly help development by bringing

in Flex when using remote services.

replicate validation annotations in order to use the Flex side validation framework

 Known Limitations

Gas3 does not support inner classes

must declare your classes in separated source files if you want them to be correctly handled by the generator