Author: jbalunas(a)redhat.com Date: 2011-02-18 13:06:24 -0500 (Fri, 18 Feb 2011) New Revision: 21781 Modified: trunk/archetypes/rf-gae-sample/readme.txt trunk/archetypes/rf-gae-sample/src/main/resources/archetype-resources/readme.txt Log: RF-10531 updated readme with encryption information Modified: trunk/archetypes/rf-gae-sample/readme.txt =================================================================== --- trunk/archetypes/rf-gae-sample/readme.txt 2011-02-18 18:00:36 UTC (rev 21780) +++ trunk/archetypes/rf-gae-sample/readme.txt 2011-02-18 18:06:24 UTC (rev 21781) @@ -1,4 +1,4 @@ -RichFaces 4 Archetype +RichFaces 4 Google Application Engine Archetype GENERATING THE PROJECT @@ -23,15 +23,20 @@ 4) Once uploaded, visit your application using http://<application-name>.appspot.com 4.1) check all the information about deployed application at https://appengine.google.com/dashboard?&app_id=<your-application-i... -NOTE: -During build the "org.richfaces.cdk:maven-resource-plugin" executed and generated static resources(web-app\static-resources\) for all skins in order to +NOTEs: +--)During build the "org.richfaces.cdk:maven-resource-plugin" executed and generated static resources(web-app\static-resources\) for all skins in order to solve the compatibility problem with GAE and java2D API. -NOTE: about additional artifacts in webapp folder: -1) java-gae-jsf-ri - contains modified WebConfiguration.java class which will be put to Web-inf\classes when building with GAE profile. It solves compatibilities +--) We have configured the MyFaces encryption secret values in the /webapp-gae/WEB-INF/web.xml. We have used "RichFacesTmpKey" as the base64 encoded SECRET values. It is wise to change the base encryption for any type of public application whether using MyFaces or Mojarra. + +See below for more information: + MyFaces - http://wiki.apache.org/myfaces/Secure_Your_Application + Mojarra - http://wikis.sun.com/display/GlassFish/JavaServerFacesRI#JavaServerFacesR... + +--) java-gae-jsf-ri - contains modified WebConfiguration.java class which will be put to Web-inf\classes when building with GAE profile. It solves compatibilities issues exist in GAE for JSF applications. -2) Webapp-gae folder contains GAE descriptor(appengine-web.xml) and modified application web.xml. They will be placed in the WEB-INF folder. The web.xml +--) Webapp-gae folder contains GAE descriptor(appengine-web.xml) and modified application web.xml. They will be placed in the WEB-INF folder. The web.xml is different in order to use static resources generated by plugin instead of dynamic resources. And also restricts threading with com.sun.faces.enableThreading context parameter as GAE not allows threads. Modified: trunk/archetypes/rf-gae-sample/src/main/resources/archetype-resources/readme.txt =================================================================== --- trunk/archetypes/rf-gae-sample/src/main/resources/archetype-resources/readme.txt 2011-02-18 18:00:36 UTC (rev 21780) +++ trunk/archetypes/rf-gae-sample/src/main/resources/archetype-resources/readme.txt 2011-02-18 18:06:24 UTC (rev 21781) @@ -1,6 +1,15 @@ -RichFaces 4 Archetype +RichFaces 4 Google Application Engine Archetype -1) Build by running: +GENERATING THE PROJECT + +This archetype creates a simple RichFaces 4 application with all the settings and custom artifacts you need to perform deploy to GAE cloud. + +1) To generate a project from the archetype, run + + mvn archetype:generate -DarchetypeGroupId=org.richfaces.archetypes -DarchetypeArtifactId=richfaces-archetype-gae -DarchetypeVersion=<richfaces-version> + -DgroupId=<yourGroupId> -DartifactId=<yourArtifactId> -Dversion=1.0-SNAPSHOT + +2) Navigate into the new project directory and build by running: mvn clean install *BEFORE NEXT STEP: @@ -9,20 +18,25 @@ -- Download and install the GAE SDK for deployment and local server tools 3) Execute appcfg from GAE SDK to publish to your account: - appcfg update <PATH: "generated-application-target-folder/output application folder"> + appcfg update <PATH: "generated-application-target-folder/output application folder"> 4) Once uploaded, visit your application using http://<application-name>.appspot.com 4.1) check all the information about deployed application at https://appengine.google.com/dashboard?&app_id=<your-application-i... -NOTE: -During build the "org.richfaces.cdk:maven-resource-plugin" executed and generated static resources(web-app\static-resources\) for all skins in order to +NOTEs: +--)During build the "org.richfaces.cdk:maven-resource-plugin" executed and generated static resources(web-app\static-resources\) for all skins in order to solve the compatibility problem with GAE and java2D API. -NOTE: about additional artifacts in webapp folder: -1) java-gae-jsf-ri - contains modified WebConfiguration.java class which will be put to Web-inf\classes when building with GAE profile. It solves compatibilities +--) We have configured the MyFaces encryption secret values in the /webapp-gae/WEB-INF/web.xml. We have used "RichFacesTmpKey" as the base64 encoded SECRET values. It is wise to change the base encryption for any type of public application whether using MyFaces or Mojarra. + +See below for more information: + MyFaces - http://wiki.apache.org/myfaces/Secure_Your_Application + Mojarra - http://wikis.sun.com/display/GlassFish/JavaServerFacesRI#JavaServerFacesR... + +--) java-gae-jsf-ri - contains modified WebConfiguration.java class which will be put to Web-inf\classes when building with GAE profile. It solves compatibilities issues exist in GAE for JSF applications. -2) Webapp-gae folder contains GAE descriptor(appengine-web.xml) and modified application web.xml. They will be placed in the WEB-INF folder. The web.xml +--) Webapp-gae folder contains GAE descriptor(appengine-web.xml) and modified application web.xml. They will be placed in the WEB-INF folder. The web.xml is different in order to use static resources generated by plugin instead of dynamic resources. And also restricts threading with com.sun.faces.enableThreading context parameter as GAE not allows threads.