EJB3 is great. Don't hesitate to use it. On Dec 14, 2012, at 8:12 AM, Martin Nagl <[email protected]> wrote:
> Putting tapestry jars in shared folder to have them loaded by common class > loader seems not quite right to me. Its a hack :) My high level feeling is: > > 1. Tapestry can provide IOC and JPA support in scope of 1 web application. > 2. If I need IOC and JPA (and EJB) support in scope of multiple web > applications, I need to delegate this to full application server (e.g. > Glassfish, TomEE, etc). > > Looks like I can not avoid EJB if I want multiple WARs to share services. > > > > -- > View this message in context: > http://tapestry.1045711.n5.nabble.com/Sharing-the-Registry-instance-between-web-applications-deployed-in-the-same-container-tp5718686p5718720.html > Sent from the Tapestry - User mailing list archive at Nabble.com. > > --------------------------------------------------------------------- > To unsubscribe, e-mail: [email protected] > For additional commands, e-mail: [email protected] > --------------------------------------------------------------------- To unsubscribe, e-mail: [email protected] For additional commands, e-mail: [email protected]
