Hi Magnus. I am using the latest glassfish 3.1 and tapestry 5.3. Although I didn't disable it I am not using live reloading. We use 'skinny' wars ( tapestry is installed into glassfish itself ) which makes redeploy nearly instantaneous. Also glassfish keeps session states across redeploy which makes hot deploy possible in production as well. I have not been successful getting glassfish HA enabled and working properly though which isn't a huge deal for us. Maybe they will fix it in he future.
On Jul 13, 2011, at 2:43 AM, Magnus Kvalheim <mag...@kvalheim.dk> wrote: > Hi Lenny, > Which version of glassfish? And have you been successful in getting > tapestry's live class reload working there? > > best regards > Magnus Kvalheim > > On Tue, Jul 12, 2011 at 6:58 PM, Lenny Primak <lpri...@hope.nyc.ny.us>wrote: > >> Thanks, Igor! Change in Tapestry is not required. >> I was using Persistens.createEntityManagerFactory() from ousite EJB or >> tapestry IOC >> which is apparently a big no-no which isn't documented anywhere besides >> stackoverflow.com >> >> On Jul 12, 2011, at 9:50 AM, Igor Drobiazko wrote: >> >>> What was your fix? Is a change in Tapestry required? >>> >>> On Tue, Jul 12, 2011 at 2:14 PM, Lenny Primak <lpri...@hope.nyc.ny.us >>> wrote: >>> >>>> I finally figured out what the problem here is. >>>> I was 'leaking EntityManagerFactory objects. They can only be used >> within >>>> SessionBeans or such, >>>> or be closed manually. >> >> --------------------------------------------------------------------- >> To unsubscribe, e-mail: users-unsubscr...@tapestry.apache.org >> For additional commands, e-mail: users-h...@tapestry.apache.org >> >> --------------------------------------------------------------------- To unsubscribe, e-mail: users-unsubscr...@tapestry.apache.org For additional commands, e-mail: users-h...@tapestry.apache.org
