On 5/18/07, Howard Lewis Ship <[EMAIL PROTECTED]> wrote:
Please add an issue to JIRA. We should extend the Reuest and/or Session API
to include a method for resetting the Session. With T5's structure, we have
a natural place to invalidate the HttpSession after sending the client
redirect.
Doe
http://tapestry.apache.org/tapestry5/tapestry-core/guide/persist.html
maybe this help:
flash strategy - "Values are stored into the session, but then deleted from
the session as they are first used to restore a page's state."
or this
default values - "This value is retained and used to reset the value of the
field at the end of each request, before the page is re
Please add an issue to JIRA. We should extend the Reuest and/or Session API
to include a method for resetting the Session. With T5's structure, we have
a natural place to invalidate the HttpSession after sending the client
redirect.
On 5/18/07, Marcus <[EMAIL PROTECTED]> wrote:
Hi,
In T4, I f
Hi,
In T4, I feel certain you know, we're using:
Logout
but in T5, sorry.
Thank's
Marcus
Hi,
the ASO are not the problem, the @Persist variables are a problem.
To the pdf: i open the page which generates the pdf by " Or klick here to
get a pdf. " in a new window. Did u mean that?
Marcus-11 wrote:
>
> HI Sabine,
>
> Maybe this help:
>
> "Assigning null to an ASO field will remov
HI Sabine,
Maybe this help:
"Assigning null to an ASO field will remove the ASO (reading the field
subsequently will force a new ASO instance to be created)."
http://tapestry.apache.org/tapestry5/tapestry-core/guide/appstate.html
By the way, you post a message about open PDF, do you know how
