On Fri, 14 Nov 2014 15:27:51 -0200, Ivano Luberti <lube...@archicoop.it>
wrote:
So B is created in the first page but not bound to the session while
some way is visible across pages
While A is created at server start-up (why?) but is not visible in the
page.
If from web.xml I remove
<listener>
<listener-class>it.archicoop.met.obliterazione.beans.User</listener-class>
</listener>
If you declare your User class like this, for the listening itself, the
servlet container will create a single User instance and invoke its
methods. This is completely unrelated to Tapestry's @SessionState. Why are
you doing that? Using the same class for this listener *and* as an
@SessionState field makes no sense at all, at least at first.
Shouldn't your User class implement HttpSessionBindingListener instead?
--
Thiago H. de Paula Figueiredo
Tapestry, Java and Hibernate consultant and developer
http://machina.com.br
---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscr...@tapestry.apache.org
For additional commands, e-mail: users-h...@tapestry.apache.org
