[jboss-cvs] JBossAS SVN: r99882 - projects/docs/enterprise/EWP_5.0/Administration_And_Configuration_Guide/en-US.

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

Author: laubai
Date: 2010-01-25 03:02:42 -0500 (Mon, 25 Jan 2010)
New Revision: 99882

Modified:
   projects/docs/enterprise/EWP_5.0/Administration_And_Configuration_Guide/en-US/EJB3.xml
Log:
Partial correction of EJB3.xml.

Modified: projects/docs/enterprise/EWP_5.0/Administration_And_Configuration_Guide/en-US/EJB3.xml
===================================================================
--- projects/docs/enterprise/EWP_5.0/Administration_And_Configuration_Guide/en-US/EJB3.xml	2010-01-25 08:00:34 UTC (rev 99881)
+++ projects/docs/enterprise/EWP_5.0/Administration_And_Configuration_Guide/en-US/EJB3.xml	2010-01-25 08:02:42 UTC (rev 99882)
@@ -10,7 +10,7 @@
        <indexterm><primary>EJB3</primary><see>Enterprise Applications with EJB3 Services</see></indexterm>
 	EJB3 (Enterprise Java Bean 3.0) provides the core component model for Java EE 5 applications. An EJB3 bean is a managed component that is automatically wired to take advantage of all services the Java EE 5 server container provides, such as transaction, security, persistence, naming, dependency injection, etc. The managed component allows developers to focus on the business logic, and leave the cross-cutting concerns to the container as configurations. As an application developer, you need not create or destroy the components yourself. You only need to ask for an EJB3 bean from the Java EE container by its name, and then you can call its methods with all configured container services applied. You can get access to an EJB3 bean from either inside or outside of the Java EE container. </para>
 	
-<para>JBoss Enterprise Web Platform 5 supports EJB3 out of the box. Note that JBoss Enterprise Web Platform 4.2 is a J2EE server, so it does not support the full EJB3 feature set. </para>
+<para>JBoss Enterprise Web Platform 5 supports EJB3 out of the box.<!-- Note that JBoss Enterprise Web Platform 4.2 is a J2EE server, so it does not support the full EJB3 feature set. --></para>
 	
 	<para>The details of the EJB3 component programming model is beyond the scope of this guide. Most EJB3 interfaces and annotations are part of the Java EE 5 standard and hence they are the same for all Java EE 5 compliant application servers. Interested readers should refer to the EJB3 specification or numerous EJB3 books to learn more about EJB3 programming.</para>
 	
@@ -39,9 +39,11 @@
 ]]>
         </programlisting>
 		
-	<para>When you invoke a session bean method, the method execution is automatically managed by the transaction manager and the security manager in the server. You can specify the transactional or security properties for each method using annotations on the method. A session bean instance can be reused by many clients. Depending on whether the server maintains the bean's internal state between two clients, the session bean can be stateless or stateful. Depending on whether the bean has a remote business interface clients outside of the current JVM can call upon the EJB3 bean. All these are configurable via standard annotations on the beans.  Note that the transactional or security properties are only active when the bean is called through a business interface.</para>
+	<para>When you invoke a session bean method, the method execution is automatically managed by the transaction manager and the security manager in the server. You can specify the transactional or security properties for each method using annotations on the method.</para>
+    
+    <para>A session bean instance can be reused by many clients. Depending on whether the server maintains the bean's internal state between two clients, the session bean can be stateless or stateful. Depending on whether the bean has a remote business interface clients outside of the current JVM can call upon the EJB3 bean. All these are configurable via standard annotations on the beans. Note that the transactional or security properties are only active when the bean is called through a business interface.</para>
 		
-	<para>After you define a session bean, how does the client get a reference to it? As we discussed, the client does not create or destroy EJB3 components, it merely asks the server for a reference of an existing instance managed by the server. That is done via JNDI. In JBoss AS, the default local JNDI name for a session bean is dependent on the deployment packaging of the bean class.</para>
+	<para>After you define a session bean, how does the client get a reference to it? As we discussed, the client does not create or destroy EJB3 components, it merely asks the server for a reference of an existing instance managed by the server. That is done via JNDI. In JBoss Enterprise Web Platform, the default local JNDI name for a session bean is dependent on the deployment packaging of the bean class.</para>
 		
 		<itemizedlist>
           <listitem><para>If the bean is deployed in a standalone JAR file in the <literal>JBOSS_DIST/default/deploy</literal> directory, the bean is accessible via local JNDI name <literal>MyBean/local</literal>, where <literal>MyBean</literal> is the implementation class name of the bean as we showed earlier. The "local" JNDI in JBoss AS means that the JNDI name is relative to <literal>java:comp/env/</literal>.</para></listitem>