Hello Angelo, Main question is do you want to use EJB in your app or not, because usually there is no proper way to share state between multiple WAR's deployed inside the application container.
Renat On 04/02/2008, Angelo Chen <[EMAIL PROTECTED]> wrote: > > > 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] > > -- Best regards, Renat Zubairov
