Author: dan.j.allen Date: 2010-02-26 03:08:17 -0500 (Fri, 26 Feb 2010) New Revision: 5963 Modified: doc/trunk/reference/en-US/gettingstarted.xml Log: add note about asadmin deploy Modified: doc/trunk/reference/en-US/gettingstarted.xml =================================================================== --- doc/trunk/reference/en-US/gettingstarted.xml 2010-02-26 08:05:13 UTC (rev 5962) +++ doc/trunk/reference/en-US/gettingstarted.xml 2010-02-26 08:08:17 UTC (rev 5963) @@ -254,10 +254,10 @@ </para> <para> - You deploy applications to GlassFish using the <ulink url="http://localhost:4848">GlassFish Admin + One way to deploy applications to GlassFish is by using the <ulink url="http://localhost:4848">GlassFish Admin Console</ulink>. To get the Admin Console running, you need to start a GlassFish domain, in our case - <literal>domain1</literal>. Switch to the <literal>bin</literal> folder in the directory where you - installed GlassFish and execute the following command: + <literal>domain1</literal>. Switch to the <literal>bin</literal> folder in the directory where you installed + GlassFish and execute the following command: </para> <programlisting><![CDATA[$> asadmin start-domain domain1]]></programlisting> @@ -275,6 +275,12 @@ </para> <para> + Alternatively, you can deploy the application to GlassFish using the asadmin command: + </para> + + <programlisting><![CDATA[$> asadmin deploy target/weld-numberguess.war]]></programlisting> + + <para> The reason the same artifact can be deployed to both JBoss AS and GlassFish, without any modifications, is because all of the features being used are part of the standard platform. And what a capable platform it has become!