You are viewing a plain text version of this content. The canonical link for it is here.
Posted to users@tapestry.apache.org by DenisGL <de...@gmail.com> on 2012/09/01 09:57:21 UTC
Re: Request Filter not called if declared with addInstance (vs add)
Thanks a lot; but, in fact, the issue is not with constraints; with
"after:CheckForUpdates,before:URLRewriter" the behavior is the same.
In fact, it has to do with parameter injection, as you supposed : with
addInstance, I see no log, but the code is executed.
--
View this message in context: http://tapestry.1045711.n5.nabble.com/Request-Filter-not-called-if-declared-with-addInstance-vs-add-tp5715859p5715958.html
Sent from the Tapestry - User mailing list archive at Nabble.com.
Re: Request Filter not called if declared with addInstance (vs add)
Posted by DenisGL <de...@gmail.com>.
So, is there any mean to log onto the real class when a logger in injected in
that class ?
--
View this message in context: http://tapestry.1045711.n5.nabble.com/Request-Filter-not-called-if-declared-with-addInstance-vs-add-tp5715859p5715964.html
Sent from the Tapestry - User mailing list archive at Nabble.com.
---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@tapestry.apache.org
For additional commands, e-mail: users-help@tapestry.apache.org
Re: Request Filter not called if declared with addInstance (vs add)
Posted by DenisGL <de...@gmail.com>.
I think I got It:
- when logger is @Inject'ed in my module and passed as my filter constructor
parameter, the messages are logged in the name of my module class
- when logger is automatically injected in my filter, the messages are
logged in the name of
"org.apache.tapestry5.services.TapestryModule.RequestHandler"
In my config, tapestry log level was set to "info", and my project to all;
which explains the issue.
--
View this message in context: http://tapestry.1045711.n5.nabble.com/Request-Filter-not-called-if-declared-with-addInstance-vs-add-tp5715859p5715963.html
Sent from the Tapestry - User mailing list archive at Nabble.com.
---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@tapestry.apache.org
For additional commands, e-mail: users-help@tapestry.apache.org
Re: Request Filter not called if declared with addInstance (vs add)
Posted by Lance Java <la...@googlemail.com>.
> With
"after:CheckForUpdates,before:URLRewriter" the behavior is the same.
You can't comma separate constraints in a single string like this. Use two
strings in the varargs method.
Try using system.out.println instead (or a debug breakpoint) but I doubt
that tapestry is logging at different log levels.
Re: Request Filter not called if declared with addInstance (vs add)
Posted by DenisGL <de...@gmail.com>.
It's an issue with log levels :
when logger is @Inject'ed in my module and used as new myRequestFilter()
parameter, it logs at trace level.
when logger is injected as a parameter (when I use addInstance), it logs at
"info" level ?!
--
View this message in context: http://tapestry.1045711.n5.nabble.com/Request-Filter-not-called-if-declared-with-addInstance-vs-add-tp5715859p5715959.html
Sent from the Tapestry - User mailing list archive at Nabble.com.
---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@tapestry.apache.org
For additional commands, e-mail: users-help@tapestry.apache.org