[jboss-cvs] JBossAS SVN: r62382 - trunk/embedded/docs/tutorial/tomcat.

[jboss-cvs-commits at lists.jboss.org]

Author: bill.burke at jboss.com
Date: 2007-04-17 17:51:50 -0400 (Tue, 17 Apr 2007)
New Revision: 62382

Modified:
   trunk/embedded/docs/tutorial/tomcat/README.html
   trunk/embedded/docs/tutorial/tomcat/README.wiki
Log:
finish distribution

Modified: trunk/embedded/docs/tutorial/tomcat/README.html
===================================================================
--- trunk/embedded/docs/tutorial/tomcat/README.html	2007-04-17 18:46:06 UTC (rev 62381)
+++ trunk/embedded/docs/tutorial/tomcat/README.html	2007-04-17 21:51:50 UTC (rev 62382)
@@ -12,34 +12,11 @@
 <li> <i>builtin.war</i> Ant target just builds a regular war file.  No special things were configured in web.xml.  For this example, you need to turn on default scanning at the Tomcat level.  Here's how.</li>
 </ul>
 </p><p>
+After deploying the WAR to Tomcat, you can access <a href="http://localhost:8080/embedded-jboss/EmbeddedJBoss.jsp">EmbeddedJBoss.jsp</a> to test the example.
 </p><p>
-<h2> Scanning every WAR by default</h2>
-
 </p><p>
-Perhaps the simplest way to deploy your EJBs, datasources, and other JBoss components is to put these .jars and files directly in the <tt>WEB-INF/lib</tt> and <tt>WEB-INF/classes</tt> directories of your deployed web apps.  You can have Embedded JBoss automatically scan each and every web app Tomcat deploys for JBoss components.  To do this you modify the default context configuration file of tomcat located in <tt>apache-tomcat/conf/context.xml</tt> and add the Embedded JBoss <tt>org.jboss.embedded.tomcat.WebinfScanner</tt> listener class.
+<b>PLEASE NOTE</b>: To find out more on how to install and bootstrap Embedded JBoss in Tomcat, please see our <a href="http://wiki.jboss.org/wiki/Wiki.jsp?page=EmbeddedJBoss">Wiki</a>
 </p><p>
-<b>context.xml</b>
-<pre>
-&lt;!-- The contents of this file will be loaded for each web application --&gt;
-&lt;Context&gt;
-
-    &lt;!-- Default set of monitored resources --&gt;
-    &lt;WatchedResource&gt;WEB-INF/web.xml&lt;/WatchedResource&gt;
-
-    &lt;!-- Uncomment this to disable session persistence across Tomcat restarts --&gt;
-    &lt;!--
-    &lt;Manager pathname="" /&gt;
-    --&gt;
-</pre>
-<b><pre>
-  &lt;Listener className="org.jboss.embedded.tomcat.WebinfScanner" /&gt;</pre></b>
-<pre>
-
-&lt;/Context&gt;
-</pre>
-</p><p>
-The advantage of this approach is that you do not have to put any special configuration in your WAR files to deploy JBoss components.  The disadvantage is that deployment time may slow down as deployers like the EJB3 container need to scan every .jar file for classes annotated with EJB3 annotations.
-</p><p>
 </p>
 </body>
 </html>

Modified: trunk/embedded/docs/tutorial/tomcat/README.wiki
===================================================================
--- trunk/embedded/docs/tutorial/tomcat/README.wiki	2007-04-17 18:46:06 UTC (rev 62381)
+++ trunk/embedded/docs/tutorial/tomcat/README.wiki	2007-04-17 21:51:50 UTC (rev 62382)
@@ -6,30 +6,8 @@
 * ''finegrain.war'' Ant target builds the war.  This war's [web.xml|resources/finegrain.web.xml] sets up a Listener that explicitly loads one particular resource from the ServletContext.
 * ''builtin.war'' Ant target just builds a regular war file.  No special things were configured in web.xml.  For this example, you need to turn on default scanning at the Tomcat level.  Here's how.
 
+After deploying the WAR to Tomcat, you can access [EmbeddedJBoss.jsp|http://localhost:8080/embedded-jboss/EmbeddedJBoss.jsp] to test the example.
 
-!!! Scanning every WAR by default
 
-Perhaps the simplest way to deploy your EJBs, datasources, and other JBoss components is to put these .jars and files directly in the {{WEB-INF/lib}} and {{WEB-INF/classes}} directories of your deployed web apps.  You can have Embedded JBoss automatically scan each and every web app Tomcat deploys for JBoss components.  To do this you modify the default context configuration file of tomcat located in {{apache-tomcat/conf/context.xml}} and add the Embedded JBoss {{org.jboss.embedded.tomcat.WebinfScanner}} listener class.
+__PLEASE NOTE__: To find out more on how to install and bootstrap Embedded JBoss in Tomcat, please see our [Wiki|http://wiki.jboss.org/wiki/Wiki.jsp?page=EmbeddedJBoss]
 
-__context.xml__
-{{{
-<!-- The contents of this file will be loaded for each web application -->
-<Context>
-
-    <!-- Default set of monitored resources -->
-    <WatchedResource>WEB-INF/web.xml</WatchedResource>
-
-    <!-- Uncomment this to disable session persistence across Tomcat restarts -->
-    <!--
-    <Manager pathname="" />
-    -->
-}}}
-__{{{
-  <Listener className="org.jboss.embedded.tomcat.WebinfScanner" />}}}__
-{{{
-
-</Context>
-}}}
-
-The advantage of this approach is that you do not have to put any special configuration in your WAR files to deploy JBoss components.  The disadvantage is that deployment time may slow down as deployers like the EJB3 container need to scan every .jar file for classes annotated with EJB3 annotations.
-