OK, so the whole mechanism does work correctly, but only if the stale
session occurs when the user is accessing an ExternalLink. In that
case, storing the serviceParameters in the ExternalCallback is
sufficient for getting good values to deal with during
activateExternalPage(). Unfortunately, it
Nope, same problem from within validate() instead of pageValidate(),
so the javadoc for ExternalCallback appears to be just plain old
incorrect. Bummer.
--sam
On 6/20/06, Sam Gendler <[EMAIL PROTECTED]> wrote:
Judging by the javadoc example in ExternalCallback, if I overlod the
validate() met
Judging by the javadoc example in ExternalCallback, if I overlod the
validate() method instead of implementig pageValidateListener, I will
be able to do what i need to do. Is there any reason not to do this,
since validate() doesn't appear to actually be deprecated?
--sam
On 6/20/06, Sam Gendl
So the entire ExternalCallback/ExternalPage thing is actually entirely
worthless when it comes to handling something like remembering where
they were going when they failed to authenticate? That seems odd,
especially since it is called out as being suitable for exactly that
in the tapestry pdf bo
Not a fun circumstance I'm sure. It's still probably better than getting
NPE's.
At the point when your pageValidate() method is called I'm not sure if you
are in the right "state" to even bother looking for the parameters this way.
The majority of requests in Tapestry end up going through the Dir
