Author: dan.j.allen
Date: 2009-11-09 14:48:53 -0500 (Mon, 09 Nov 2009)
New Revision: 4888
Modified:
examples/trunk/jsf/permalink/readme.txt
Log:
add urls
Modified: examples/trunk/jsf/permalink/readme.txt
===================================================================
--- examples/trunk/jsf/permalink/readme.txt 2009-11-09 18:54:19 UTC (rev 4887)
+++ examples/trunk/jsf/permalink/readme.txt 2009-11-09 19:48:53 UTC (rev 4888)
@@ -15,6 +15,20 @@
Now you are ready to deploy.
+== Deploying to JBoss AS
+
+If you run a normal Maven build, the artifact it produces is deployable to JBoss
+AS by default:
+
+ mvn package
+
+Just copy target/weld-permalink.war to the JBoss AS deploy directory. Open this
+local URL to access the running application:
+
+
http://localhost:8080/weld-permalink
+
+But you may want to take advantage of the embedded servlet containers.
+
== Deploying with an embedded servlet container
Run this command to execute the application in an embedded Jetty 6 container:
@@ -25,6 +39,10 @@
mvn war:inplace tomcat:run -Ptomcat
+You can access the application for either container at the following local URL:
+
+
http://localhost:9090/weld-permalink
+
In both cases, any changes to assets in src/main/webapp take effect immediately.
If a change to a webapp configuration file is made, the application may
automatically redeploy. The redeploy behavior can be fine-tuned in the plugin
@@ -81,6 +99,10 @@
mvn war:exploded tomcat:redeploy -Ptomcat
mvn compile war:exploded tomcat:redeploy -Ptomcat
+The application is available at the following local URL:
+
+
http://localhost:8080/weld-permalink
+
= Importing the project into Eclipse
The recommended way to setup a Seam example in Eclipse is to use the m2eclipse