User: salborini
Date: 00/10/31 09:57:54
Modified: . ejbref_howto.html
Removed: . ejbref_howto1.html
Log:
Fixed typo, removed duplicate file
Revision Changes Path
1.2 +2 -2 jbossweb/ejbref_howto.html
Index: ejbref_howto.html
===================================================================
RCS file: /products/cvs/ejboss/jbossweb/ejbref_howto.html,v
retrieving revision 1.1
retrieving revision 1.2
diff -u -r1.1 -r1.2
--- ejbref_howto.html 2000/09/01 23:53:47 1.1
+++ ejbref_howto.html 2000/10/31 17:57:54 1.2
@@ -29,7 +29,7 @@
</p>
<p>To be allowed this call, the bean A must declare it in the its deployment
descriptor. This is done by an <tt><ejb-ref></tt> tag in the bean section of the
<em>ejb-jar.xml</em> file. 2 cases may occur:
<ul>
- <li><b>Internal ejb reference</b>: the bean B is in the same
application unit as the bean A. This means that the beans are physically packaged in
the same jar. In this case, you must provide the<ejb-link>tag, and its value must
match the<ejb-name>of bean B. You don't have to provide anything in the jboss.xml
file. Your <em>ejb-jar.xml</em> file will look like this:
+ <li><b>Internal ejb reference</b>: the bean B is in the same
application unit as the bean A. This means that the beans are physically packaged in
the same jar. In this case, you must provide the <tt><ejb-link></tt> tag, and
its value must match the <tt><ejb-name></tt> of bean B. You don't have to
provide anything in the jboss.xml file. Your <em>ejb-jar.xml</em> file will look like
this:
<p>
<table border="0" bgcolor="#80ff80" cellspacing="4">
<tr>
@@ -70,7 +70,7 @@
</tr>
</table>
</p>
- <li><b>External ejb reference</b>: the bean B comes from another
application unit, it may even be deployed on another server. This means that the
beans live in different jars on different systems. In this case, you cannot rely on
the standard <ejb-link> tag in ejb-jar.xml since there the beans are not covered in
the same file. Instead, you must provide the full jndi name of the bean B in
jboss.xml. This is necessary to map the names from different ejb-jar.xml files since
the 2 beans are defined in different application units. A full name is of the form
+ <li><b>External ejb reference</b>: the bean B comes from another
application unit, it may even be deployed on another server. This means that the
beans live in different jars on different systems. In this case, you cannot rely on
the standard <tt><ejb-link></tt> tag in ejb-jar.xml since there the beans are
not covered in the same file. Instead, you must provide the full jndi name of the bean
B in jboss.xml. This is necessary to map the names from different ejb-jar.xml files
since the 2 beans are defined in different application units. A full name is of the
form
<pre>protocol://host:1234/name/in/other/server</pre>
<p>Note that the <tt><ejb-ref-name></tt> tags in the 2 xml files
must match.
<p><em>ejb-jar.xml</em>:</p>
