[jboss-dev-forums] [Design of EJB 3.0] - Plug-able default JNDI binding policy

[bdecoste]

This is something we've discussed in the past, but it's come up again. I propose that we create a plug-able default jbndi policy. It's becoming clear that no matter what we choose for a default policy, somebody doesn't like it. SEAM is having problems with embedded in multiple wars and would like the default policy to be warName/bean/Name.

 I don't think it would be that much work - maybe a day or 2. The jndi code is fairly isolated now. Here's what we would need to do

- create the policy api. Probably just 1 method like 

  | String getJndiBinding(String deploymentName, String beanName, boolean
  | isLocal, isHome);
  | 

- create an impl for the current policy
- create an annotation like @JndiPolicy for setting the policy impl
- modify ejb3-interceptors-aop.xml to default the default policy
- modify the jboss.xml schema and code to add the new annotation

Thoughts? 

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

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