That's the PerThread scope.
Tapestry IoC was designed to do minimal intrusion into your code; until
5.2, it didn't do field injection, just constructor injection.
The problem with saying "@SessionScope is not supported" is that, if you
iterate over all the fields and all the annotation, how do yo
Maybe I do net get it, but why can't you make use of a service having "Request
Scope"? So Tapestry creates a new Instance per Request and you attach / inject
yor session here?
Jens
Sent from my iPhone
On 17.06.2013, at 15:50, Michael Gentry wrote:
> Could Tapestry throw an exception if you u
No. Services are handled by Tapestry-IoC and @SessionState isn't part of
it. In other words, we would need to create a dependency of Tapestry-IoC on
Tapestry(-core, the web framework), something that doesn't happen today.
On Mon, Jun 17, 2013 at 10:50 AM, Michael Gentry wrote:
> Could Tapestry t
Could Tapestry throw an exception if you use @SessionState in a service?
Thanks,
mrg
On Mon, Jun 17, 2013 at 9:25 AM, Thiago H. de Paula Figueiredo <
thiag...@gmail.com> wrote:
> On Mon, Jun 17, 2013 at 8:36 AM, Nathan Quirynen <
> nat...@pensionarchitects.be> wrote:
>
> > Hi,
> >
>
> Hello!
On Mon, Jun 17, 2013 at 8:36 AM, Nathan Quirynen <
nat...@pensionarchitects.be> wrote:
> Hi,
>
Hello!
>
> I think the problem is that I use the @SessionState in a injected service.
> And the service being a singleton, explains the behaviour. I guess
> @SessionState can only be used in pages an
I made the mistake of using
@SessionState in a service, while this is only supported in pages
components or mixins.
So the annotation didn't do anything. So there was always just one
instantiation of the object, which everyone used.
I fixed my problem
Hi,
I think the problem is that I use the @SessionState in a injected
service. And the service being a singleton, explains the
behaviour. I guess @SessionState can only be used in pages and
components? Have to test this though.
On 17/06/13 13:0
A common mistake is to initialize @Persist or @SessionState fields in its
declaration (such as @Persist private User user = new User(). Don't do
that. Use event handler methods for that. setupRender() is usually a good
choice.
On Mon, Jun 17, 2013 at 5:49 AM, Nathan Quirynen <
nat...@pensionarchi
can you post some code? the page with the annotated field and the methods
that manipulate that fields?
On Mon, Jun 17, 2013 at 10:49 AM, Nathan Quirynen <
nat...@pensionarchitects.be> wrote:
> Hi,
>
> I'm having some weird issues with sessions that are getting mixed up, for
> example:
>
> I open
Hi,
I'm having some weird issues with sessions that are getting mixed up,
for example:
I open a page in both Firefox and Safari (so they are a different
HttpSession).
I do something in Firefox that sets a value in an object that is
annotated with @SessionState.
Apparently this change also a
10 matches
Mail list logo
