No luck? That sucks. =/
I thought occured to me just before I fell asleep last night, though.
Perhaps you should store the messages directly in your pages instead and
pass them on to your layout? That's how I would do it, anyhow.
You could wrap the add functions in a MessageHolder class that you can
easily pass to your layout. Maybe that will work...
-Filip
zack1403 skrev:
Yea I've tried multiple different combinations of @Persist to get something
to work on my pages and component with no luck. Thanks anyways for your
help Filip.
Zack
Filip S. Adamsen-2 wrote:
You say you added @Persist("flash") to your pages, but the information
you're storing doesn't go into the page, but into the component. I think
you'll have to put @Persist("flash") on your list of messages in your
Layout component.
If that doesn't solve it, I'm afraid I don't know what the problem is.
Hopefully someone else will be able to help you, then.
-Filip
On 2008-05-23 01:20, zack1403 wrote:
Filip,
One of the first things I added was @Persist("flash") to my pages with no
luck. Still the same behavior. Even with the pages pooled should they
share attribute values across sessions?
Filip S. Adamsen-2 wrote:
Working as intended. Tapestry uses a page pool which means that you have
to use some sort of persistence to make this work:
http://tapestry.apache.org/tapestry5/tapestry-core/guide/persist.html
-Filip
On 2008-05-23 00:45, zack1403 wrote:
No. Not using any persist. I really dont have anything else besides a
title
and this list of messages. When I move from page to page I might
inject
my
layout and add a message to this list for display. They get persisted
without any sort of persist.
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
