Yes! I forgot about that. Works like a charm :)
On Tue, Sep 14, 2010 at 1:46 PM, Guerin Laurent wrote:
> Hi,
>
> From tapestry 5.2 you can use @SessionAttribute.
>
> Envoyé de mon iPhone
>
> Le 14 sept. 2010 à 20:34, "Adam Zimowski" a écrit :
>
>>> I find it both easy and self-descriptive to wri
Hi,
From tapestry 5.2 you can use @SessionAttribute.
Envoyé de mon iPhone
Le 14 sept. 2010 à 20:34, "Adam Zimowski" a
écrit :
I find it both easy and self-descriptive to write wrapper classes
for these java objects.
That's exactly what I'm trying to avoid. With a large team of junior
p
> I find it both easy and self-descriptive to write wrapper classes for these
> java objects.
That's exactly what I'm trying to avoid. With a large team of junior
programmers this will be a maintenance nightmare.
> You could always grab the HttpSession and store them yourself.
>From my searchin
> I understand that @SessionState was meant for POJOs. What's the
> preferred (if any) way in Tapestry to store Strings, Integers and such
> across multiple pages?
It really depends on the use case. If you can bundle them up into a
class that'd be the best way. For instance, if you're storing some
I'm not sure if this is the recommended way, but I find it both easy and
self-descriptive to write wrapper classes for these java objects so you
can use either SessionState or the Environment to move them across pages
in the application. For example, if you have a String for the name of
the use
I understand that @SessionState was meant for POJOs. What's the
preferred (if any) way in Tapestry to store Strings, Integers and such
across multiple pages?
Adam
-
To unsubscribe, e-mail: users-unsubscr...@tapestry.apache.org
Fo
