Thank you, this works fine.
Of course, now I can't remember the example that made me think this
approach wouldn't work!
Thanks again
On Mon, Jul 5, 2010 at 12:33 PM, Pedro Santos wrote:
> UI state as properties in the component should be to fine, see if using
> session relative urls the problem
UI state as properties in the component should be to fine, see if using
session relative urls the problem remains
On Mon, Jul 5, 2010 at 4:10 PM, Anh <7za...@gmail.com> wrote:
> Hi,
>
> I'm having trouble on how to best implement something simple:
>
> I'm frequently finding the need to have 2 Mod
Wicket stores the "state" (its fields) of a component (and thus pages)
between requests. So, your idea should work. Did you see any
serialization errors/warnings on your output log? Perhaps the
component's state can't be serialized?
On Mon, Jul 5, 2010 at 3:10 PM, Anh <7za...@gmail.com> wrote:
Hi,
I'm having trouble on how to best implement something simple:
I'm frequently finding the need to have 2 Models for a component:
One Model is the bound data object (persisted),
The other is lightweight UI state, such as whether a section is expanded, etc.
The UI state is not needed outside of
