On Tue, 4 Mar 2003, Scott M Stark wrote: > 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?
These ejb-refs could have been defined outside of the invoker element. Invoker-specific ejb-refs make sense when you have multiple invokers per EJB. They are not really needed in the bankiiop testcase, which uses a single invoker (the IIOP invoker). I have probably placed them within the invoker element just because their jndi-names are IIOP-specific. If you have multiple invokers per EJB, invoker-specific ejb-refs act as a kind of "multivalued link" from the bean ENC to a set of JNDI names (one per invoker). Such a "multivalued link" allows outgoing invocations to be transparently performed through the same protocol (invoker) as the current invocation. The particular JNDI name seen at the end of the "multivalued link" depends on the invoker through which the current invocation arrived. The bean code just uses an ejb-ref, such as "ejb/Bank". If the bean code runs within an IIOP invocation, "ejb/Bank" means "iiop/bank/Bank", which is bound to a CORBA IOR. If the same code runs within a JRMP invocation, "ejb/Bank" could mean "bank/Bank", which would be bound to a serialized JRMP proxy. Cheers, Francisco ------------------------------------------------------- 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
