es' is different I figure there must
> somehow be a different logger at work.
> I already tried pluggin in the vanilla logging.properties from the tapestry
> 5 archetype but nothing changes.
>
> Anyone got any clue where to look?
>
> p.s: I'm running in Tomcat 5.5 doe
thing to do with it?
--
View this message in context:
http://n2.nabble.com/T5-logging-statements-logged-twice-using-Log4j-tp4597599p4597599.html
Sent from the Tapestry Users mailing list archive at Nabble.com.
-
To unsubs
Hi,
Following the link at end of this post, i made a IOC only app, it works.
then I added a logging like this:
@Inject
private Logger logger;
import org.slf4j.Logger;
but I got:
No service implements the interface org.slf4j.Logger.
any idea how to register the logger manually?
Thanks,
You want to look into how to configure log4j, assuming your using the
default logging implementation.
On Tue, Jul 8, 2008 at 12:49 AM, Angelo Chen <[EMAIL PROTECTED]>
wrote:
>
> hi,
>
> i just noticed that catalina.out contains informations from different web
> apps hosted in the same site, is th
hi,
i just noticed that catalina.out contains informations from different web
apps hosted in the same site, is there a way for me to specify a log file
for my tapestry 5 app only? thanks.
Angelo
--
View this message in context:
http://www.nabble.com/t5%3A-logging-pages-tp18333788p18333788.html
Hi Angelo,
I don't Dispatcher is the most convenient place to put this, a
RequestFilter seems like a better option since you have easy access to
the name of the page, parameters, and whatnot.
It'd basically be the same as creating an authentication filter but you
would do logging instead.
Hi,
I would like to keep a log of visits made by viewers, what page he goes,
from what IP he comes, etc. what is a good place to do this, a dispatcher?
or any good suggestions in adding a logging facility in T5? Thanks,
Angelo
--
View this message in context:
http://www.nabble.com/t5%3A-loggin
I think this is an excellent suggestion.
On Jan 4, 2008 12:48 PM, Will Norris <[EMAIL PROTECTED]> wrote:
>
> On Jan 4, 2008, at 11:56 AM, Will Norris wrote:
>
> > Perhaps a specific string can be prepended to T5 framework log
> > messages, so that they can be filtered out in the logger
> > configu
On Jan 4, 2008, at 11:56 AM, Will Norris wrote:
Perhaps a specific string can be prepended to T5 framework log
messages, so that they can be filtered out in the logger
configuration? Is that already possible by some global
configuration, or should I add an issue?
Even better, I think I
Actually we're not talking about log4j category loggers... we're
talking about slf4j loggers. I point that out only because I'm using
logback, not log4j. Nevertheless, I think I've found a good enough
solution for the time being... adding an appender filter. The primary
offender in the D
I'm sorry, but no. They do not come from different loggers. What are
you talking about?
We are talking about log4j category loggers. And tapestry is using the
classname of the page, and we're using the classname of the page (which
is the standard), and hence we can't change the loglevel of what
You can differentiate. They come from different loggers.
You can configure log4j(if that's what your using) to ignore(or send to
another appender) DEBUG and TRACE messages from Tapestry.
Will Norris wrote:
My concern isn't ERROR and FATAL messages being lost in the noise...
that can easily be
My concern isn't ERROR and FATAL messages being lost in the noise...
that can easily be done with some logging configuration as you've
suggested. My concern is my own DEBUG and TRACE messages being lost
in the noise, since there is no way to differentiate my own messages
from those generat
One of the easiest things you can do to combat this problem is to configure
logging to output log messages from your application to a separate log file and
yet another output for all of those critical ERROR and FATAL messages so
they don't get lost in the noise that easily.
Kalle
On 1/4/08, Fern
+1
We are in the same boat:
I also dislike the fact that tapestry spits out the generated javacode
using the classname of the page, such that we can't filter it out.. it's
also hard for us to pay attention to any debug output during the first
few requests.
Will Norris wrote:
> I'm running into
I'm running into what must be a common "problem" (bug or feature, you
decide) though I can't find much info about it in the list archives or
online. I'm becoming continually frustrated by the fact that the
TRACE and DEBUG log levels are rendered basically useless for pages
and components b
16 matches
Mail list logo
