I am using Tapestry 3.0.3 and 1.4.2 of the JVM. I seem to be having a problem where my Visit object is becoming null when I do not want it to. The Visit object is created by a getVisit() call when the user first logs into the application.
The first page the user sees works with the Visit object to display dynamic text. They can then click on some direct links on the page or submit a form with information. This first page displays without any problem. The first page extends the class Protected which is taken from the Virtual Library example. Protected implements pageValidateListener and does a check to see that there is a not NULL visit object and that a boolean is set properly inside the visit object. It is when they first click on a direct link or submit a form the page does some work and reloads. The visit object is fine when they click on submit or a direct link. However, when the page reloads to display to the user the result of clicking on a link or submitting the form the pageValidation catches that the Visit object is null. This only happens on the production servers and not on the development machines. But I am not sure what if any this extra fact implies. I hope to hear from anyone who has ever had an issue where their visit object just becomes null at a completly unexpected time or event. --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
