Thank both of you!
I'll analyze these options.
Anyway, I am curious about why my approach is not working, I insist, is it
a bug?
Best regards,
Matias.
On Sun, Sep 23, 2012 at 10:58 AM, Matías Blasi matias.bl...@gmail.comwrote:
Hi all,
I'm trying to implement a mechanism to track each user
On Tue, 25 Sep 2012 10:03:04 -0300, Matías Blasi matias.bl...@gmail.com
wrote:
Thank both of you!
I'll analyze these options.
Anyway, I am curious about why my approach is not working, I insist, is
it a bug?
Session is not a service, so it cannot be advised.
--
Thiago H. de Paula
() a NoSuchMethodException is being thrown.
I can only assume that tapestry is using the service id (session) instead
of the interface (org.apache.tapestry5.services.Session) to lookup the
object to advise.
--
View this message in context:
http://tapestry.1045711.n5.nabble.com/Advisin-Tapestry
Thanks Thiago,
It is a surprise for me! Because, it is into the services package... and
I'd be pretty sure about injecting it... but I would be wrong
Anyway, something is confusing me, because my @Advise annotation is
explicitly pointing to this interface:
On Tue, 25 Sep 2012 10:56:03 -0300, Matías Blasi matias.bl...@gmail.com
wrote:
Thanks Thiago,
De nada! :)
It is a surprise for me! Because, it is into the services package...
and I'd be pretty sure about injecting it... but I would be wrong
In this case, you're wrong. :) Not
Thanks, done: https://issues.apache.org/jira/browse/TAP5-2002!
Best regards,
Matias.
On Tue, Sep 25, 2012 at 11:17 AM, Thiago H de Paula Figueiredo
thiag...@gmail.com wrote:
On Tue, 25 Sep 2012 10:56:03 -0300, Matías Blasi matias.bl...@gmail.com
wrote:
Thanks Thiago,
De nada! :)
://tapestry.apache.org/5.3.5/apidocs/org/apache/tapestry5/internal/services/TapestrySessionFactory.html
--
View this message in context:
http://tapestry.1045711.n5.nabble.com/Advisin-Tapestry-Session-tp5716457p5716464.html
Sent from the Tapestry - User mailing list archive at Nabble.com
Hi all,
I'm trying to implement a mechanism to track each user session, at least
the login and logout events.
The login is easy, because it occurs in a defined place, but the logout can
occurs explicitly or because of a timeout, so I thought in advising the
Tapestry Session.invalidate() method:
I can't answer your specific question, but as an alternative approach
(and not tied to Tapestry) you could implement an HttpSessionListener,
like this (and configure it in your web.xml):
import javax.servlet.http.HttpSessionEvent;
import javax.servlet.http.HttpSessionListener;
import
