Is it better to have hibernate persistence layer put inside another classloader/jvm so that others can also access. As of now we have tapestry /spring/hibernate coming up in a single classloader. If hibernate is to be accessed by weblogic integration, should that be put inside a EJB jar file?
This is a real project issue. We need Weblogic integration to do workflow activities. And how could we integrate all these technologies in ideal way. As of now we are planning to bring up spring in tapestry UI(to communicate to workflow/EJB) as well as within the EJB (to do hibernate persistence).
Also is it enough that Spring application context be registered at one place in JNDI tree so that multiple EJBs/WARs cann access the same application context?
In a multitiered environment is it always better to register applicationContext to JNDI of the environment?
Thanks in Advance,