It makes Hibernate working as Jboss MBean service, this service is responsible for working with Hibernate sessions. This way leaves you only with JBoss, without any alternative.
2008/2/4, Jonathan Barker <[EMAIL PROTECTED]>: > Angelo, > > Take a look at JBoss .har files. I've never tried it but it might be a way > to share a common Hibernate setup among multiple webapps. > > Jonathan > > > -----Original Message----- > > From: Angelo Chen [mailto:[EMAIL PROTECTED] > > Sent: Sunday, February 03, 2008 8:28 PM > > To: users@tapestry.apache.org > > Subject: T5: best practice for a multiple module app > > > > > > Hi, > > A mini ERP project which will contains ar, ap, gl, inventory and some > > others, if every module is a single Tapestry 5 application, then we have 4 > > modules, all modules should share the same persistence store, UI is > > independent from each other, however there are some linkage as well, > > example, in the ap module user might be able to select an invoice from > > inventory, what is the best practice to structure this kind of app? pure > > Tapestry app? or ejb/seam based with T5 as the web tier? thanks. > > -- > > View this message in context: http://www.nabble.com/T5%3A-best-practice- > > for-a-multiple-module-app-tp15260841p15260841.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] > > --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
