> 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 searching the mailing list, this seems like the only viable
option. I try to stay away from using Servlet API, but may have to as
a work around. Anything better?

Adam

On Tue, Sep 14, 2010 at 11:42 AM, Josh Canfield <joshcanfi...@gmail.com> wrote:
>> 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
> shared user configuration you could create a UserConfiguration object
> with the values. Your class could be a simple wrapper around
> Properties, or a Map if you need something more flexible than fixed
> properties.
>
> You could always grab the HttpSession and store them yourself...
>
>
>>
>> Adam
>>
>> ---------------------------------------------------------------------
>> To unsubscribe, e-mail: users-unsubscr...@tapestry.apache.org
>> For additional commands, e-mail: users-h...@tapestry.apache.org
>>
>>
>
>
>
> --
> --
> http://www.bodylabgym.com - a private, by appointment only, one-on-one
> health and fitness facility.
> --
> http://www.ectransition.com - Quality Electronic Cigarettes at a
> reasonable price!
> --
> TheDailyTube.com. Sign up and get the best new videos on the internet
> delivered fresh to your inbox.
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: users-unsubscr...@tapestry.apache.org
> For additional commands, e-mail: users-h...@tapestry.apache.org
>
>

---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscr...@tapestry.apache.org
For additional commands, e-mail: users-h...@tapestry.apache.org

Reply via email to