[jboss-dev-forums] [Design of EJB 3.0] - Scope of the Proxy Component

ALRubinger do-not-reply at jboss.com
Wed May 14 03:49:11 EDT 2008


Carlo, you've defined a test in EJB3 Proxy which goes beyond scope of the Proxy component. :)

Because we've granted jboss-metadata the authority/responsibility to define the resolved JNDI names, Proxy's job ends so long as lookups and invocations to the JNDI name obtained from metadata succeed.  We can't have tests looking for bindings in any particular form (ie. MyStatelessBean/remote).

Because Proxy will be getting the JNDI names from metadata, just as the Client container does, it doesn't matter what the JNDI names are; they'll match.

If we want to check that JNDI names follow the exected format, those tests belong in jboss-metadata alongside the DefaultJndiBindingPolicy implementations.

S,
ALR

View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4150607#4150607

Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=4150607



More information about the jboss-dev-forums mailing list