[jboss-dev-forums] [Design of EJB 3.0] - Re: JBossEjbParsingDeployer can't handle EJB3 jboss.xml
scott.stark@jboss.org
do-not-reply at jboss.com
Tue Jun 26 12:36:11 EDT 2007
I think we should be moving to a common EjbDeployer with different reference policies controlling how the reference is handled (injected or just a jndi binding). Same for the legacy ejb interceptors vs the spec interceptors and aop interceptors. Ideally we should be able to use the new aop interceptors with ejb 2.x components with the new ejb3 container and just drop the old stuff.
I don't want to get too bogged down in supporting this unified view out of the gate for 5.0.0 though. Let's just start refactoring the ejb3 layer with that as the ultimate goal.
View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4057782#4057782
Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=4057782
More information about the jboss-dev-forums
mailing list