Hello Remy,
Remy Maucherat schrieb:
Thorsten Kamann wrote:
hello Remy, hello Peter,
I am following your dicussion about the new logging in the tomcat cvs.
I have some question about this changes: 1. Old configurations in the server.xml and <context>.xml is not valid, because the old logger with <Logger ... /> is defined? 2. How can I automatically configure Log4J to add new categrories if the a host/context added or removed? 3. At wich place the logs will be written if the configuration is not properly set?
Our comapny uses the tomcat as a hosting solution for our customers. Every customer has access to his own logs. The logger can be set of the coustomers themselves in their context.xml, of course. Is this behaviour broken after your refactoring is done?
A lot of stuff will be broken in this branch. There was no way for me to continue improving Tomcat without breaking stuff. OTOH, I expect the relatively bug free 5.0.x branch to live for a long time, so don't plan upgrading (other than the connector refactoring, there won't be any major reason to upgrade existing installations; this branch is designed for new setups).
When this branch is so very different from the current 5.0.x, why ist thne name not 6.x? And why is there no chance to use the old configuration and redirects internal to the new logger implementation?
About logging:
- it is a mistake (nowadays) to define custom loggers in applications (JBoss doesn't, and yet it's far more complex); of course, an equally big mistake is to provide "logging" services in the Servlet API ;)
This is only a dream. In a hosting enviroment every customer will logging different. We offer own logfiles with the <Logger> configuartion in the context.xml. This were broken, if your changes are kept.
My greatest problem is the administration of the log4j configuration. Where - or better - how can I do this automatically. This question you don't answer? Is there a discussion done about this problem?
Your logger solution is maybe is well solution for a development or company-intern-used tomcat installation but the UseCase "Webhosting" have been ignored. If I must administrate every customer logger manually this is very counterproductively.
- the big problem which I want to solve here is that logs are going to different places, which is wrong; now, all logs should go to commons-logging (or directly to the actual logger that commons-logging is wrapping)
What do you mean with "different places". If you man different places the logs will be saved than can I say this is a normal behaviour. In Germany there is a admin tool called "Confixx". This tool saves the logs in the home directory of the user. Than the user can view and load his logs with a normal ftp-client.
Best regards Thorsten
-- Thorsten Kamann Email: [EMAIL PROTECTED] ICQ: 40746578 Yahoo: ThorQue
--------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
