[jboss-dev-forums] [Design of EJB 3.0] - Re: Pluggable @EJB Resolvers

[wolfc]

I'm contemplating whether to change the supply/demand chain as well. It can work with only JNDI names. In which case we would get:
interface EJBDependencyResolver {
  |    /** @return JNDI name */
  |    String resolveEJBReference(DeploymentUnit deploymentUnit, String beanName, Class<?> beanInterface, String mappedName);
  | }
At leat 1 argument must be specified. mappedName is for unforeseens, because now it's the JNDI name.

For WS it's a bit different, because they can invoke any public method on a bean. So they can't invoke through the current proxies.

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

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