You are viewing a plain text version of this content. The canonical link for it is here.
Posted to commits@beehive.apache.org by cs...@apache.org on 2007/02/09 00:21:09 UTC
svn commit: r505085 -
/beehive/trunk/docs/forrest/release/src/documentation/content/xdocs/system-controls/ejb/guide.xml
Author: cschoett
Date: Thu Feb 8 15:21:08 2007
New Revision: 505085
URL: http://svn.apache.org/viewvc?view=rev&rev=505085
Log:
A bit of cleanup to the EJB system control developer guide.
Modified:
beehive/trunk/docs/forrest/release/src/documentation/content/xdocs/system-controls/ejb/guide.xml
Modified: beehive/trunk/docs/forrest/release/src/documentation/content/xdocs/system-controls/ejb/guide.xml
URL: http://svn.apache.org/viewvc/beehive/trunk/docs/forrest/release/src/documentation/content/xdocs/system-controls/ejb/guide.xml?view=diff&rev=505085&r1=505084&r2=505085
==============================================================================
--- beehive/trunk/docs/forrest/release/src/documentation/content/xdocs/system-controls/ejb/guide.xml (original)
+++ beehive/trunk/docs/forrest/release/src/documentation/content/xdocs/system-controls/ejb/guide.xml Thu Feb 8 15:21:08 2007
@@ -54,9 +54,8 @@
<td>jndiName</td>
<td>String</td>
<td>No</td>
- <td>Specifies the JNDI name of the target EJB's home interface
- (e.g. EJBNameHome). This value may also be an URL using the "JNDI:"
- protocol (e.g. jndi://username:password@host:port/EJBNameHome).
+ <td>
+ Specifies the JNDI name of the target EJB's home interface (e.g. EJBNameHome).
</td>
</tr>
<tr>
@@ -73,11 +72,12 @@
</section>
<section>
<title>The JNDIContextEnv Annotation</title>
- <p>JNDIContextEnv specifies the environment properties for the JNDI context that will
+ <p>
+ JNDIContextEnv specifies the environment properties for the JNDI context that will
be used to lookup the target EJB. It is an optional class-level annotation for the EJB
- Control.</p>
- <p> If using a URL with the "JNDI:" protocol or to use a JNDI context with the
- default envirnoment properties, this annotation is not necessary.</p>
+ Control. To use a JNDI context with the default envirnoment properties, this annotation is
+ not necessary.
+ </p>
<table>
<tr><th>Member Name</th><th>Value Type</th><th>Value Required</th><th>Description</th></tr>
<tr>
@@ -158,29 +158,10 @@
</section>
<section>
- <title>Accessing EJBs on a Different Server</title>
- <p>You can access EJBs on a different server with an EJB control, provided the server hosting the EJB
- control and the server to which the target EJB is deployed are in the same domain. You access EJBs
- on a different server by using special JNDI syntax in the <code>EJBHome</code> annotation's <code>jndiName</code>
- attribute.</p>
-
- <p>For example:</p>
- <source>
- @EJBHome(jndiName="jndi://username:password@host:7001/my.resource.jndi.object")
- </source>
-
- <p>You can also use environment properties to specify configuration information, such as:</p>
-
- <source>
- @EJBHome(jndiName="jndi://host:7001/MyEJBHome?SECURITY_PRINCIPAL=me&SECURITY_CREDENTIALS=passwd")
- </source>
- </section>
-
- <section>
<title>Creating an EJB Control</title>
<p>The EJB Control is an extensible control, and you do not use it directly.
To create an EJB control for an EJB, you would create a control extending the EJB Control.
- An extended EJB control can only represent one EJB, so you must create one for each EJB.</p>
+ An extended EJB control can only represent one EJB, so you must create a new extended control for each EJB.</p>
<p>The following steps should be observed:</p>
<ol>
@@ -189,7 +170,7 @@
if it is an entity bean, extend <code>org.apache.beehive.controls.system.ejb.EntityEJBControl</code>.
</li>
<li>Annotate the Java interface with @ControlExtension (<code>org.apache.beehive.controls.api.bean.ControlExtension</code>),
- so the Control Annotation Processor will know that the Java interface is a control extension.
+ so the control annotation processor will know that the Java interface is a control extension.
</li>
<li>Have the Java interface also extend the EJB's home and business interfaces. The business interface
may either by the EJB's local interface or the remote interface.