OK,
the reason for duplicated messages was a misconfiguration in
log4j.properties - there were 2 appenders down the path to my package with
level 'DEBUG'.
The 'WARN' level for Tapestry-debugging was set correctly.
So there are only 2 questions left :)
Thanks,
Gerald
[EMAIL PROTECTED]
An: "Tapestry users"
<[email protected]>
20.01.2006 Kopie:
00:09 Thema: Looking for 'best practice'
for logging ...
Bitte
antworten an
"Tapestry
users"
Hi !
I was just typing a mail for the list because error logging with log4j
seems to be impossible, when I restarted the tomcat-server ... ok - now
there are TONS of logging-messages :)
I think I have found the right location of the log4j.properties file now
and did a performance-test of my syslogd :)
But there are new issues :(
When doing a
logger.info("klicked") ;
in my listeners, the log-message is always displayed twice.
Is this an error in my log4j.properties/syslogd-setup even thoug
warning-messages from Tapestry/Tomcat/Hibernate are displayed only once ?
Or because I am using a
private static Logger logger = Logger.getLogger("my.package") ;
and there is some build-in logging of Tapestry I am not aware of ?
And the second issue:
The only way to change logging-behaviour at the moment is to restart the
Tomcat service.
Redeploying the war-file doesnt work :( Is there a possibility to change
this behaviour ?
And the last question :)
I this the right way to integrate logging in a tapestry-app ? Or are there
some better choices (using Hivemind-services, for example) ?
I am almost sure I am doing something forbidden here ;-)
Thank you in advance !
Bye,
Gerald
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
