[jboss-cvs] JBossAS SVN: r68023 - projects/microcontainer/trunk/docs/User_Guide/src/main/docbook.

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

Author: newtonm
Date: 2007-12-07 05:47:05 -0500 (Fri, 07 Dec 2007)
New Revision: 68023

Modified:
   projects/microcontainer/trunk/docs/User_Guide/src/main/docbook/User_Guide.xml
Log:
Clarified current thread of execution.

Modified: projects/microcontainer/trunk/docs/User_Guide/src/main/docbook/User_Guide.xml
===================================================================
--- projects/microcontainer/trunk/docs/User_Guide/src/main/docbook/User_Guide.xml	2007-12-07 10:43:15 UTC (rev 68022)
+++ projects/microcontainer/trunk/docs/User_Guide/src/main/docbook/User_Guide.xml	2007-12-07 10:47:05 UTC (rev 68023)
@@ -1112,7 +1112,7 @@
 }</programlisting>
         <para>The deploy() method takes a URL representing the location of an XML deployment descriptor and passes it as a string to an unmarshaller. The unmarshaller parses the XML,  converts it into an object representation called a  KernelDeployment and sets its name. The KernelDeployment object is  then passed to the deploy() method of the superclass BasicKernelDeployer. This iterates through all of the beans in the deployment   creating a context for each one which it subsequently passes to the contoller&apos;s install() method to peform the deployment. The controller then performs actions on each context to take the bean from one state to another: NOT_INSTALLED, DESCRIBED, CONFIGURED, INSTANTIATED, CREATE, START, INSTALLED. Once a bean reaches the INSTALLED state then it&apos;s considered to be deployed.</para>
         <important>
-          <para>During the deployment process, as the controller performs the Instantiate action, the thread context classloader is used to load the bean&apos;s class into the JVM.  As all of the controller code is executed by the thread that calls controller.install(), this is what we mean by the current thread of execution.</para>
+          <para>During the deployment process, as the controller performs the Instantiate action, the thread context classloader is used to load the bean&apos;s class into the JVM.  As all of the controller code is executed by the thread that calls controller.install() we refer to this as the  current thread of execution.</para>
         </important>
         <para>Therefore when using the BasicXMLDeployer the classloader used to load bean classes is retrieved from the thread that calls the BasicXMLDeployer&apos;s deploy() method as this goes on to call controller.install() which subsequently executes the Instantiate action. For all of our examples this is the primordial thread whose context classloader is set on startup to the classloader that loaded the application, i.e. the application classloader. This means that in our examples the microcontainer can load any bean classes present on the application, extension or boot classpaths.</para>
         <para>What happens though if we create our own threads in the application and use these to call the deploy() method of our BasicXMLDeployer?</para>