Chapter 12. Enterprise Bean Environment
143
home
tests.SS1Home
/home
remote
tests.SS1
/remote
/ejb-ref
The declaration of an EJB reference used for accessing the bean through its
local
home and component
interfaces in the standard deployment descriptor is shown in the following example:
ejb-local-ref
ejb-ref-name
ejb/locses1
/ejb-ref-name
ejb-ref-type
session
/ejb-ref-type
local-home
tests.LocalSS1Home
/local-home
local
tests.LocalSS1
/local
/ejb-local-ref
If the referred bean is defined in the same EJB-JAR or EAR file, the optional
ejb-link
element of
the ejb-ref or ejb-local-ref element can be used to specify the actual referred bean. The value of the
ejb-link element is the name of the target Enterprise Bean, that is, the name defined in the ejb-name
element of the target Enterprise Bean. If the target Enterprise Bean is in the same EAR file, but in a
different EJB-JAR file, the name of the ejb-link element should be the name of the target bean, prefixed
by the name of the containing EJB-JAR file followed by ’#’ (for example,
My_EJBs.jar#bean1
). In
the following example, the ejb-link element has been added to the ejb-ref (in the referring bean SSA)
and a part of the description of the target bean (SS1) is shown:
session
ejb-name
SSA
/ejb-name
...
ejb-ref
ejb-ref-name
ejb/ses1
/ejb-ref-name
ejb-ref-type
session
/ejb-ref-type
home
tests.SS1Home
/home
remote
tests.SS1
/remote
ejb-link
SS1
/ejb-link
/ejb-ref
...
/session
...
session
ejb-name
SS1
/ejb-name
home
tests.SS1Home
/home
local-home
tests.LocalSS1Home
/local-home
remote
tests.SS1
/remote
local
tests.LocalSS1
/local
ejb-class
tests.SS1Bean
/ejb-class
...
/session
...
If the bean SS1 is not in the same EJB-JAR file as SSA, but in another file named
product_ejbs.jar
, the ejb-link element would be:
ejb-link
product_ejbs.jar#SS1
/ejb-link
If the referring component and the referred bean are in separate files and not in the same EAR, the
current JOnAS implementation does not allow use of the ejb-link element. To resolve the reference in
this case, the
jonas-ejb-ref
element in the JOnAS-specific deployment descriptor would be used
to bind the environment JNDI name of the EJB reference to the actual JNDI name of the associated
Enterprise Bean home. In the following example, it is assumed that the JNDI name of the SS1 bean
home is SS1Home_one.
jonas-session
Summary of Contents for Application Server
Page 1: ...Red Hat Application Server JOnAS User Guide ...
Page 8: ......
Page 22: ...14 Chapter 1 Java Open Application Server JOnAS a J2EE Platform ...
Page 58: ...50 Chapter 3 JOnAS Configuration ...
Page 66: ...58 Chapter 5 JOnAS Class Loader Hierarchy ...
Page 78: ...70 Chapter 6 JOnAS Command Reference ...
Page 80: ......
Page 86: ...78 Chapter 7 Developing Session Beans ...
Page 136: ...128 Chapter 9 Developing Message Driven Beans ...
Page 142: ...134 Chapter 10 Defining the Deployment Descriptor ...
Page 148: ...140 Chapter 11 Transactional Behavior of EJB Applications ...
Page 158: ...150 Chapter 14 EJB Packaging ...
Page 162: ...154 Chapter 15 Application Deployment and Installation Guide ...
Page 164: ......
Page 176: ...168 Chapter 18 WAR Packaging ...
Page 178: ......
Page 184: ...176 Chapter 20 Defining the Client Deployment Descriptor ...
Page 186: ...178 Chapter 21 Client Packaging ...
Page 188: ......
Page 192: ...184 Chapter 23 EAR Packaging ...
Page 194: ......
Page 200: ...192 Chapter 24 JOnAS Services ...
Page 204: ...196 Chapter 25 JOnAS and the Connector Architecture ...
Page 222: ...214 Chapter 27 Ant EJB Tasks Using EJB JAR ...
Page 234: ...226 Chapter 29 Web Services with JOnAS ...
Page 236: ......
Page 260: ...252 Chapter 34 How to use Axis in JOnAS ...
Page 270: ...262 Chapter 36 Web Service Interoperability between JOnAS and BEA WebLogic ...
Page 296: ......