On Wed, 18 Mar 2015 11:14:08 -0300, Poggenpohl, Daniel
wrote:
What I meant to say was they recommend @SessionState instead of
@SessionAttribute because it is a complex object.
Who said that? Anyway, I think it's an incorrect statement. It should say
"@SessionAttribute for primitive types
nd then do a manual merge() or via DAO on it.
Can I inject into my AppSession object or what would be the way to go here?
Regards,
Daniel P.
-Ursprüngliche Nachricht-
Von: Thiago H de Paula Figueiredo [mailto:thiag...@gmail.com]
Gesendet: Mittwoch, 18. März 2015 14:17
An: Tapestry us
On Wed, 18 Mar 2015 07:21:06 -0300, Poggenpohl, Daniel
wrote:
Hello again,
Hi!
I need a session storage where I store the currently logged on user.
Reading about it in the documentation, they recommend using
@SessionState because my user is a complex object, also containing lists
of
Or is it just that entities are used under-supported this way?
>
> Regards,
> Daniel P.
>
> -Ursprüngliche Nachricht-
> Von: Barry Books [mailto:trs...@gmail.com ]
> Gesendet: Mittwoch, 18. März 2015 12:05
> An: Tapestry users
> Betreff: Re: Session Storage with T
gmail.com]
Gesendet: Mittwoch, 18. März 2015 12:05
An: Tapestry users
Betreff: Re: Session Storage with Tapestry
If you are using Tapestry Hibernate it should just work if you put a Hibernate
object into a SessionState variable. There is a configuration that contains the
Hibernate entities so SessionSt
System.out.println(group.toString());
}
}
Any pointers? Do I have to use the user as a direct SessionState object? Can't
I use a wrapper class?
Regards,
Daniel P.
Von: Poggenpohl, Daniel
Gesendet: Mittwoch, 18. März 2015 11:21
An: users@tapestry.apache.org
Betreff: Ses
If you are using Tapestry Hibernate it should just work if you put a
Hibernate object into a SessionState variable. There is a configuration
that contains the Hibernate entities so SessionState is able to store the
primary key in the session and retrieve the object when needed. Services as
well as
Hello again,
a slightly different topic as the last but with the same "undertones":
I need a session storage where I store the currently logged on user. Reading
about it in the documentation, they recommend using @SessionState because my
user is a complex object, also containing lists of other
