Thank you for clarification, Ales. I like the approach of building a special Spring deployer; we may adopt it. Still, my application resolves the same issue as the one discussed in your article, integration of EJB and Spring. It takes a more traditional approach for that task though by reading applicationContext.xml from a class path for each Session bean. The advantage of your approach, I suppose, is that the loading of teh application context will happen only once.
I beleive that reading applicationContext.xml and placing it in the JNDI tree is not dependent on EJB 3.0 and can be done with EJB 2.1, correct? Michael View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=3944606#3944606 Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=3944606 ------------------------------------------------------- Using Tomcat but need to do more? Need to support web services, security? Get stuff done quickly with pre-integrated technology to make your job easier Download IBM WebSphere Application Server v.1.0.1 based on Apache Geronimo http://sel.as-us.falkag.net/sel?cmd=lnk&kid=120709&bid=263057&dat=121642 _______________________________________________ JBoss-user mailing list [email protected] https://lists.sourceforge.net/lists/listinfo/jboss-user
