Mark, I had initially setup my hibernate to try and bind to a JNDI name created by tomcat in the server.xml and it failed to work with that, I ended up setting up hibernate to create its own JNDI name put its SessionFactory there. Then I used a Filter based plugin to give out session's and close them as needed. I'd imagine you could have your own servlet put hibernate into a JNDI name and as long as that name is available to the other webapps they could have plugins to grab sessions from that SessionFactory. -David
----- Original Message ----- From: "Mark Lowe" <[EMAIL PROTECTED]> To: "Struts Users Mailing List" <[EMAIL PROTECTED]> Sent: Wednesday, January 07, 2004 4:20 AM Subject: [ot] hibernate jndi > Has anyone any words of wisdom when it comes to configuring a jndi > service for hibernated classes that ideally only runs a service from a > webapp? > > I've been using the hibernate plugin which tends to fall over daily. > Ideally a servlet that's fired up via web.xml rather than a struts > plugin could prove more reliable. I've used this approach with torque > in the past albeit not using jndi. > > I'd prefer not to configure the service via server.xml as I don't need > the service to be global but rather contain the service to a specific > webapp or two. > > Cheers Mark > > > --------------------------------------------------------------------- > 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]
