[jboss-dev-forums] [Design of EJB 3.0] - Re: Ejb3Deployment.resolveMessageDestination

[wolfc]

As it is right now it should be dropped.

But resolvedJndiName has nothing to do with raw metadata. That's one of the reasons that I made the naming policy decorator prototype for beans. The same should be done for references (some day).

The mapped resolver deployer is becoming a big beast. It should delegate out the actual resolving function of the references and then setup the decorated metadata.

EJB3 within AS will then get references (and beans) which will always have a jndiName / mappedName, with the old fallback code refactored onto the same resolvers mapped resolver deployer is using.

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

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