Thorsten Kamann wrote:
When this branch is so very different from the current 5.0.x, why ist
thne name not 6.x?

Because it doesn't implement a new spec, and there's no release plan anyway at this time.


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.

Oh ok, so you're telling me that you expect your webapps/frameworks to log using four things then:
- ServletContext.log(java.lang.Exception exception, java.lang.String msg) (deprecated one ;) )
- ServletContext.log(java.lang.String msg)
- ServletContext.log(java.lang.String message, java.lang.Throwable throwable) (the all powerful one, you can do everything with that)
- System.out.println if you did configure swallowOutput (I like that one :D )
I must be an idiot I think this is not the case. This discussion is closed from my side, since what you write doesn't make any sense.


Rémy


--------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]



Reply via email to