tapestry5 double form submit handled?

2012-08-05 Thread Angelo C.
Hi, Does t5 handle double submit issues? Angelo -- View this message in context: http://tapestry.1045711.n5.nabble.com/tapestry5-double-form-submit-handled-tp5715083.html Sent from the Tapestry - User mailing list archive at Nabble.com. --

Re: Ajax errors handling

2012-08-05 Thread Lenny Primak
Flowlogix tapestry library does this the redirect-on-logout and session expired handling http://code.google.com/p/flowlogix/ On Aug 5, 2012, at 10:56 PM, Matías Blasi wrote: > Hi all, > > I'm interested on handling ajax requests errors in some way to integrate > them with the alerts mechanism

Ajax errors handling

2012-08-05 Thread Matías Blasi
Hi all, I'm interested on handling ajax requests errors in some way to integrate them with the alerts mechanism (jGrowl) if its possible. I think that I should contribute some errorHandler to the tapestry javascript library, am I right? Also, it would be usefull to detect a session expired/forbi

Re: Misleading PerthreadManagerImpl memory leak?

2012-08-05 Thread Howard Lewis Ship
On Sun, Aug 5, 2012 at 1:25 AM, petr.charvat wrote: > My application uses tapestry 5.3.4 and I deploy it on Tomcat 6.0.35. > The internal tomcat listener JreMemoryLeakPreventionListener write to > console this message after undeploy/redeploy my application. > > 5.8.2012 9:23:18 org.apache.catalina

Misleading PerthreadManagerImpl memory leak?

2012-08-05 Thread petr.charvat
My application uses tapestry 5.3.4 and I deploy it on Tomcat 6.0.35. The internal tomcat listener JreMemoryLeakPreventionListener write to console this message after undeploy/redeploy my application. 5.8.2012 9:23:18 org.apache.catalina.loader.WebappClassLoader clearThreadLocalMap SEVERE: The web

Hidden component semantics changed (was Re: [5.3.4] Ordering of Actions...)

2012-08-05 Thread robert baker
Howard (and list), After doing some more research, I found the issue, and it didn't have anything to do with the ordering of render phases (I apologize for that). What happened was that the ValueEncoder in question was coded to create a blank object (i.e. "null object" pattern) on a null value in