Hi!
Sebastien Alborini wrote:
> > Trying to get my Bank examples to run, and found a bug in the
> > EjbRefMetadata class. There are two ways to resolve an "ejb-ref": either
> > to a name of an EJB in the same app ("internal link"), or to a full
> > JNDI-name ("external link"). Internal links are defined in the
> > ejb-jar.xml file as "ejb-link", and external links are in jboss.xml as
> > "jndi-name".
>
> Not quite sure I follow you. What is, or should be, the technical
> difference in jboss between an internal and an external link? Can't
> they both be LinkRefs in JNDI?
Nope. The internal link should be directly bound to the linked beans
home (since we have it internally), and an external link is just a
LinkRef(externalJndiName). External links can be to a bean in a Weblogic
server somewhere.
> > Currently, if "ejb-link" is given that is interpreted as an external
> > link. If it is not given the "home" element is used to resolve the link.
> > BOTH of these are wrong. "ejb-link" given -> internal link. Not given ->
> > unresolved link that should be caught by the verifier.
>
> Is the jboss.xml section really needed? Can't we just look for a bean
> that matches the class names? (that was the use of my
> ApplicationMetadata.getJndiFromHome(), from jboss1.0)
We could, but wouldn't recommend it. There may be several beans with a
given home/remote combo.
> > EjbRefMetaData must be updated with correct semantics, and BeanMetaData
> > must also be updated to account for the jboss.xml information.
> > Sebastien, you are set as author, can you make these changes please?
>
> Sure, as soon as I get it :)
Clearer?
/Rickard
--
Rickard �berg
Email: [EMAIL PROTECTED]
http://www.telkel.com
http://www.jboss.org
http://www.dreambean.com
