...
The following four examples would yield the same jndi names. The intention with these examples is to show the various ways you can isolate specific interfaces or types of interfaces to gain more specific control on how they are named.
| Code Block |
|---|
|
<openejb-jar>
...
<session>
...
<jndi name="LocalOne" interface="org.superbiz.LocalOne"/>
<jndi name="LocalTwo" interface="org.superbiz.LocalTwo"/>
<jndi name="RemoteOne" interface="org.superbiz.RemoteOne"/>
<jndi name="RemoteTwo" interface="org.superbiz.RemoteTwo"/>
<jndi name="FooHome" interface="org.superbiz.FooHome"/>
<jndi name="FooLocalHome" interface="org.superbiz.FooLocalHome"/>
</session>
</openejb-jar>
|
| Code Block |
|---|
|
<openejb-jar>
...
<session>
...
<!-- applies to LocalOne and LocalTwo -->
<jndi name="{interfaceClass.simpleName}" interface="Local"/>
<!-- applies to RemoteOne and RemoteTwo -->
<jndi name="{interfaceClass.simpleName}" interface="Remote"/>
<!-- applies to FooHome -->
<jndi name="{interfaceClass.simpleName}" interface="RemoteHome"/>
<!-- applies to FooLocalHome -->
<jndi name="{interfaceClass.simpleName}" interface="LocalHome"/>
</session>
</openejb-jar>
|
| Code Block |
|---|
|
<openejb-jar>
...
<session>
...
<!-- applies to RemoteOne, RemoteTwo, FooHome, and FooLocalHome -->
<jndi name="{interfaceClass.simpleName}"/>
<!-- these two would count as an override on the above format -->
<jndi name="LocalOne" interface="org.superbiz.LocalOne"/>
<jndi name="LocalTwo" interface="org.superbiz.LocalTwo"/>
</session>
</openejb-jar>
|
| Code Block |
|---|
|
<openejb-jar>
...
<session>
...
<!-- applies to LocalOne, LocalTwo, RemoteOne, RemoteTwo, FooHome, and FooLocalHome -->
<jndi name="{interfaceClass.simpleName}"/>
</session>
</openejb-jar>
|
...
