You can create a PageCallback instance and store it into the session. See
here:
http://tapestry.apache.org/current/apidocs/org/apache/tapestry5/PageCallback.html
On Thu, Dec 23, 2010 at 8:47 PM, nick567 wrote:
>
>
> Thiago H. de Paula Figueiredo wrote:
> >
> > I can't see why this would be more
Thiago H. de Paula Figueiredo wrote:
>
> I can't see why this would be more trouble the any other use of session
> persistence.
>
Just so I'm not misunderstood, we will be taking the recommended approach of
storing the page name, rather than the instance.
Howard put forth the idea of possibly
On Thu, 23 Dec 2010 13:54:12 -0200, nick567 wrote:
https://issues.apache.org/jira/browse/TAP5-1386
Not sure about storing the id/pagename when it's marked @Persist, that
sounds like it's asking for trouble! :)
I can't see why this would be more trouble the any other use of session
persisten
Thanks for the info, I added an issue to change the error message.
https://issues.apache.org/jira/browse/TAP5-1386
Not sure about storing the id/pagename when it's marked @Persist, that
sounds like it's asking for trouble! :)
Thanks,
Nick
--
View this message in context:
http://tapestry.10457
Pages are not persistent; what you had in 5.1 would never have worked in a
cluster, and probably would have acted strangely otherwise.
5.1 should not have allowed it.
The bug here is that 5.2 does a poor job explaining this; please add an
issue for better message saying "pages and components may
Hello! I am doing an upgrade from 5.1.0.5 to 5.2.4. I discovered that you
can't mark a page @Persist in 5.2, though this was allowed in 5.1:
public class TestFile {
@Persist
private TestFile nextPage;
}
In 5.2, it gives this error: "java.lang.RuntimeException: Class
application.pages.Te
