The jboss_3_2.dtd was way out of date with respect to the container
invoker configuration so I updated it and checked it in. Take a look
at this and see if there are other missing elements or elements that
should be dropped.
One construct that I don't understand in the invoker-bindings/invoker
elements are the ejb-ref child elements. For example, this setup
from the bankiiop testcase:
<session>
<ejb-name>Teller</ejb-name>
<jndi-name>bank/Teller</jndi-name>
<configuration-name>Standard Stateless SessionBean</configuration-name>
<invoker-bindings>
<invoker>
<invoker-proxy-binding-name>iiop</invoker-proxy-binding-name>
<ejb-ref>
<ejb-ref-name>ejb/Customer</ejb-ref-name>
<jndi-name>iiop/bank/Customer</jndi-name>
</ejb-ref>
<ejb-ref>
<ejb-ref-name>ejb/Account</ejb-ref-name>
<jndi-name>iiop/bank/Account</jndi-name>
</ejb-ref>
<ejb-ref>
<ejb-ref-name>ejb/Bank</ejb-ref-name>
<jndi-name>iiop/bank/Bank</jndi-name>
</ejb-ref>
</invoker>
</invoker-bindings>
</session>
What is the purpose of the invoker binding specific ejb-refs?
It still just a link from the bean ENC to a JNDI name so why
are then under the invoker-bindings?
xxxxxxxxxxxxxxxxxxxxxxxx
Scott Stark
Chief Technology Officer
JBoss Group, LLC
xxxxxxxxxxxxxxxxxxxxxxxx
-------------------------------------------------------
This SF.net email is sponsored by: Etnus, makers of TotalView, The debugger
for complex code. Debugging C/C++ programs can leave you feeling lost and
disoriented. TotalView can help you find your way. Available on major UNIX
and Linux platforms. Try it free. www.etnus.com
_______________________________________________
Jboss-development mailing list
[EMAIL PROTECTED]
https://lists.sourceforge.net/lists/listinfo/jboss-development