[jboss-dev-forums] [Design of EJB 3.0] - Re: Default JNDI naming scheme in EJB3.0 and possible confli
The first example is a pain, which is easily circumvented by setting another JNDI policy.
Which will be the cases when we go 3.1.
The second example will even fail in 3.1, but I consider it bad practice to have two
classes with the same name in 1 module.
View the original post :
http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4183552#...
Reply to the post :
http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&a...