You are viewing a plain text version of this content. The canonical link for it is here.
Posted to commits@tomee.apache.org by vi...@apache.org on 2012/01/25 02:43:48 UTC
svn commit: r803231 - in /websites/production/openejb: ./
content/jndi-names.html
Author: vishwanathk
Date: Wed Jan 25 01:43:48 2012
New Revision: 803231
Log:
Correct alignment and show as table
Modified:
websites/production/openejb/ (props changed)
websites/production/openejb/content/jndi-names.html
Propchange: websites/production/openejb/
------------------------------------------------------------------------------
--- svn:mergeinfo (original)
+++ svn:mergeinfo Wed Jan 25 01:43:48 2012
@@ -1 +1 @@
-/websites/staging/openejb/trunk:790824-803203
+/websites/staging/openejb/trunk:790824-803230
Modified: websites/production/openejb/content/jndi-names.html
==============================================================================
--- websites/production/openejb/content/jndi-names.html (original)
+++ websites/production/openejb/content/jndi-names.html Wed Jan 25 01:43:48 2012
@@ -76,9 +76,10 @@
<h1>What's My Bean's JNDI Name?</h1>
-<p>There are two things to keep in mind before you start reading:
-1. OpenEJB provides a default JNDI name to your EJB.
-1. You can customize the JNDI name.</p>
+<p>There are two things to keep in mind before you start reading:</p>
+
+<p>1 OpenEJB provides a default JNDI name to your EJB. <br />
+2 You can customize the JNDI name.</p>
<p><a name="JNDINames-DefaultJNDIname"></a></p>
@@ -96,7 +97,7 @@ name format.</p>
<p><a name="JNDINames-JNDINameFormatting"></a></p>
-<h1>JNDI Name Formatting<div class="excerpt">}</h1>
+<h1>JNDI Name Formatting</h1>
<p>The <em>openejb.jndiname.format</em> property allows you to supply a template for
the global JNDI names of all your EJBs. With it, you have complete control
@@ -105,74 +106,48 @@ right for your client apps. See the <a
doc for clever ways to use the JNDI name formatting functionality in
client code.</p>
-<p>|| variable || description ||
- | moduleId | Typically the name of the ejb-jar file or the <ejb-jar
-id=""> id value if specified |
- | ejbType | STATEFUL, STATELESS, BMP_ENTITY, CMP_ENTITY, or
-MESSAGE_DRIVEN |
- | ejbClass | for a class named <em>org.acme.superfun.WidgetBean</em> results in
-<em>org.acme.superfun.WidgetBean</em> |
- | ejbClass.simpleName | for a class named <em>org.acme.superfun.WidgetBean</em>
-results in <em>WidgetBean</em> |
- | ejbClass.packageName | for a class named <em>org.acme.superfun.WidgetBean</em>
-results in <em>org.acme.superfun</em> |
- | ejbName | The ejb-name as specified in xml or via the 'name' attribute
-in an @Stateful, @Stateless, or @MessageDriven annotation |
- | deploymentId | The unique system id for the ejb. Typically the ejbName
-unless specified in the openejb-jar.xml or via changing the
-openejb.deploymentId.format |
- | interfaceType | see interfaceType.annotationName |
- | interfaceType.annotationName | Following the EJB 3 annotations
-@RemoteHome, @LocalHome, @Remote and @Local
-- <em>RemoteHome</em> <em>(EJB 2 EJBHome)</em>
-- <em>LocalHome</em> <em>(EJB 2 EJBLocalHome)</em>
-- <em>Remote</em> <em>(EJB 3 Business Remote)</em>
-- <em>Local</em> <em>(EJB 3 Business Local)</em>
-- <em>Endpoint</em> <em>(EJB webservice endpoint)</em></p>
-
-<table>
-<tr></tr>
- | interfaceType.annotationNameLC | This is the same as
-interfaceType.annotationName, but all in lower case.
-<tr></tr>
-</table>
-
-<p>| interfaceType.xmlName | Following the ejb-jar.xml descriptor elements
-<home>, <local-home>, <business-remote>, <business-local>, and
-<service-endpoint>:
-- <em>home</em> <em>(EJB 2 EJBHome)</em>
-- <em>local-home</em> <em>(EJB 2 EJBLocalHome)</em>
-- <em>business-remote</em> <em>(EJB 3 Business Remote)</em>
-- <em>business-local</em> <em>(EJB 3 Business Local)</em>
-- <em>service-endpoint</em> <em>(EJB webservice endpoint)</em>
- |
- | interfaceType.xmlNameCc | Camel-case version of interfaceType.xmlName:
-- <em>Home</em> <em>(EJB 2 EJBHome)</em>
-- <em>LocalHome</em> <em>(EJB 2 EJBLocalHome)</em>
-- <em>BusinessRemote</em> <em>(EJB 3 Business Remote)</em>
-- <em>BusinessLocal</em> <em>(EJB 3 Business Local)</em>
-- <em>ServiceEndpoint</em> <em>(EJB webservice endpoint)</em> |
- | interfaceType.openejbLegacyName | Following the OpenEJB 1.0 hard-coded
-format:
-- <em>(empty string)</em> <em>(EJB 2 EJBHome)</em>
-- <em>Local</em> <em>(EJB 2 EJBLocalHome)</em>
-- <em>BusinessRemote</em> <em>(EJB 3 Business Remote)</em>
-- <em>BusinessLocal</em> <em>(EJB 3 Business Local)</em>
-- <em>ServiceEndpoint</em> <em>(EJB webservice endpoint)</em> |
- | interfaceClass | - <em>(business)</em> for a class named
-<em>org.acme.superfun.WidgetRemote</em> results in
-<em>org.acme.superfun.WidgetRemote</em>
- - <em>(home)</em> for a class named <em>org.acme.superfun.WidgetHome</em> results in
-<em>org.acme.superfun.WidgetHome</em></p>
-
<table>
-<tr></tr>
- | interfaceClass.simpleName | - _(business)_ for a class named
-_org.acme.superfun.WidgetRemote_ results in *WidgetRemote*
-- _(home)_ for a class named _org.acme.superfun.WidgetHome_ results in
-*WidgetHome* |
- | interfaceClass.packageName | for a class named
-_org.acme.superfun.WidgetRemote_ results in *org.acme.superfun* | <div class="excerpt">}
+<tr><td>variable</td><td> description</td></tr>
+<tr><td>moduleId</td><td> Typically the name of the ejb-jar file<br> or the <ejb-jar id=""> id value if specified</td></tr>
+<tr><td>ejbType</td><td> STATEFUL, STATELESS, BMP_ENTITY, CMP_ENTITY, or MESSAGE_DRIVEN</td></tr>
+<tr><td>ejbClass</td><td> for a class named org.acme.superfun.WidgetBean results in org.acme.superfun.WidgetBean</td></tr>
+<tr><td>ejbClass.simpleName</td><td> for a class named org.acme.superfun.WidgetBean results in WidgetBean</td></tr>
+<tr><td>ejbClass.packageName</td><td> for a class named org.acme.superfun.WidgetBean results in org.acme.superfun</td></tr>
+<tr><td>ejbName</td><td> The ejb-name as specified in xml or via the 'name' attribute in an @Stateful, @Stateless, or @MessageDriven annotation</td></tr>
+<tr><td>deploymentId</td><td> The unique system id for the ejb. Typically the ejbName unless specified in the openejb-jar.xml or via changing the openejb.deploymentId.format</td></tr>
+<tr><td>interfaceType</td><td> see interfaceType.annotationName</td></tr>
+<tr><td>interfaceType.annotationName</td><td> Following the EJB 3 annotations @RemoteHome, @LocalHome, @Remote and @Local
+RemoteHome (EJB 2 EJBHome)
+LocalHome (EJB 2 EJBLocalHome)
+Remote (EJB 3 Business Remote)
+Local (EJB 3 Business Local)
+Endpoint (EJB webservice endpoint)</td></tr>
+<tr><td>interfaceType.annotationNameLC</td><td> This is the same as interfaceType.annotationName, but all in lower case.</td></tr>
+<tr><td>interfaceType.xmlName</td><td> Following the ejb-jar.xml descriptor elements <home>, <local-home>, <business-remote>, <business-local>, and <service-endpoint>:
+home (EJB 2 EJBHome)
+local-home (EJB 2 EJBLocalHome)
+business-remote (EJB 3 Business Remote)
+business-local (EJB 3 Business Local)
+service-endpoint (EJB webservice endpoint)</td></tr>
+<tr><td>interfaceType.xmlNameCc</td><td> Camel-case version of interfaceType.xmlName:
+Home (EJB 2 EJBHome)
+LocalHome (EJB 2 EJBLocalHome)
+BusinessRemote (EJB 3 Business Remote)
+BusinessLocal (EJB 3 Business Local)
+ServiceEndpoint (EJB webservice endpoint)</td></tr>
+<tr><td>interfaceType.openejbLegacyName Following the OpenEJB 1.0 hard-coded format:
+(empty string) (EJB 2 EJBHome)
+Local (EJB 2 EJBLocalHome)
+BusinessRemote (EJB 3 Business Remote)
+BusinessLocal (EJB 3 Business Local)
+ServiceEndpoint (EJB webservice endpoint)</td></tr>
+<tr><td>interfaceClass</td><td>
+(business) for a class named org.acme.superfun.WidgetRemote results in org.acme.superfun.WidgetRemote<br>
+(home) for a class named org.acme.superfun.WidgetHome results in org.acme.superfun.WidgetHome</td></tr>
+<tr><td>interfaceClass.simpleName</td><td>
+(business) for a class named org.acme.superfun.WidgetRemote results in WidgetRemote
+(home) for a class named org.acme.superfun.WidgetHome results in WidgetHome</td></tr>
+<tr><td>interfaceClass.packageName</td><td> for a class named org.acme.superfun.WidgetRemote results in org.acme.superfun</td></tr>
</table>
<p><a name="JNDINames-SettingtheJNDIname"></a></p>