Hi All, I'm writing a web application with Tapestry 4.0 and am seeing a some sort of timeout effect. I have searched online but could not find any reference to a timeout other than the default Tomcat session timeout (which is set to 30 minutes).
The effect is the following: I have a form that on submit does some rather heavy processing on the server which can take more than 1 minute. [I know, I should eventually deal with this in some other way, optimally with some asynchronous JavaScript to replace some sort of progress bar with the actual content when it becomes available, but for the moment this is how we are doing it.] When the user presses submit and the operation takes longer than a period of time which lies between 30 seconds and 1 minute, Tapestry seems to go into some sort of timeout and reevaluates the submit method in my page object, only this time all the relevant objects from the form are set to null. I can not find any reference to any sort of additional timeout period internal to Tapestry or Hivemind and was hoping someone here could shed some light on this... -- Boris Terzic - Bringing the common hedgehog to the world.
