[weld-commits] Weld SVN: r5366 - in archetypes/trunk/jsf: jee-minimal/src/main/resources/archetype-resources and 1 other directory.

[weld-commits at lists.jboss.org]

Author: dan.j.allen
Date: 2009-12-24 03:28:18 -0500 (Thu, 24 Dec 2009)
New Revision: 5366

Modified:
   archetypes/trunk/jsf/jee-minimal/src/main/resources/archetype-resources/readme.txt
   archetypes/trunk/jsf/jee/src/main/resources/archetype-resources/readme.txt
Log:
notes


Modified: archetypes/trunk/jsf/jee/src/main/resources/archetype-resources/readme.txt
===================================================================
--- archetypes/trunk/jsf/jee/src/main/resources/archetype-resources/readme.txt	2009-12-24 08:15:27 UTC (rev 5365)
+++ archetypes/trunk/jsf/jee/src/main/resources/archetype-resources/readme.txt	2009-12-24 08:28:18 UTC (rev 5366)
@@ -24,7 +24,7 @@
 
  If you want to deploy the application to a standalone Servlet Container, then
  you will need to set one up. Alternatively, you can use a Maven command to run
- the application in place on an embedded version of GlassFish.
+ the application in place on an embedded version of GlassFish V3.
 
  Please note that Maven 2 project needs to use the JBoss Maven repository
  because there are certain Java EE API JARs that are not yet publised to the
@@ -66,7 +66,7 @@
 
   http://localhost:8080/${artifactId}
 
- If you want to deploy to GlassFish (standalone), you first need to change
+ If you want to deploy to GlassFish V3 (standalone), you first need to change
  the name of the DataSource used by the persistence unit! Open this file:
 
   src/main/resources/META-INF/persistence.xml
@@ -82,9 +82,22 @@
 
   mvn package
  
- You can now deploy the target/${artifactId}.war archive and launch the
- application the through GlassFish administration console.
+ There are several ways to deploy the archive to GlassFish V3. The recommended
+ approach is to open the project in NetBeans 6.8, right-click on the project
+ and select "Run" from the context menu. That starts JavaDB, GlassFish and
+ deploys the application.
 
+ You can also start GlassFish from the commandline. Change to the glassfish/bin
+ directory in the GlassFish install root and run these three commands:
+
+  asadmin start-database
+  asadmin start-domain domain1
+
+ Now you can either deploy the target/${artifactId}.war through the web-based
+ GlassFish admininstration console, or you can again use asadmin:
+
+  asadmin /path/to/project/target/${artifactId}.war
+
  Unfortunately, the embedded GlassFish V3 application server does not bootstrap
  the persistence unit(s), so you won't be able to leverage the Maven plugin to
  run the application in place (like you can in a jee-minimal project).

Modified: archetypes/trunk/jsf/jee-minimal/src/main/resources/archetype-resources/readme.txt
===================================================================
--- archetypes/trunk/jsf/jee-minimal/src/main/resources/archetype-resources/readme.txt	2009-12-24 08:15:27 UTC (rev 5365)
+++ archetypes/trunk/jsf/jee-minimal/src/main/resources/archetype-resources/readme.txt	2009-12-24 08:28:18 UTC (rev 5366)
@@ -23,7 +23,7 @@
 
  If you want to deploy the application to a standalone Servlet Container, then
  you will need to set one up. Alternatively, you can use a Maven command to run
- the application in place on an embedded version of GlassFish.
+ the application in place on an embedded version of GlassFish V3.
 
  Please note that Maven 2 project needs to use the JBoss Maven repository
  because there are certain Java EE API JARs that are not yet publised to the
@@ -33,7 +33,7 @@
  =========================
 
  You can deploy the application without moving any files around using the
- embedded GlassFish application server.
+ embedded GlassFish V3 application server.
 
  To run the application using embedded GlassFish, execute this command:
 
@@ -79,9 +79,22 @@
 
   http://localhost:8080/${artifactId}
 
- If you want to deploy to GlassFish (standalone), you can upload the
- target/${artifactId}.war archive using the web-based administration console.
+ There are several ways to deploy the archive to GlassFish V3 (standalone). The
+ recommended approach is to open the project in NetBeans 6.8, right-click on
+ the project and select "Run" from the context menu. That starts JavaDB,
+ GlassFish V3 and deploys the application.
 
+ You can also start GlassFish from the commandline. Change to the glassfish/bin
+ directory in the GlassFish install root and run these three commands:
+
+  asadmin start-database
+  asadmin start-domain domain1
+
+ Now you can either deploy the target/${artifactId}.war through the web-based
+ GlassFish admininstration console, or you can again use asadmin:
+
+  asadmin /path/to/project/target/${artifactId}.war
+
  Importing the project into an IDE
  =================================