- Original Message -
From: "Peter Rossbach" <[EMAIL PROTECTED]>
To: "Tomcat Developers List" <[EMAIL PROTECTED]>
Sent: Sunday, June 27, 2004 3:34 AM
Subject: Re: Please describe the new Logger System at cvs head.
> Hello Bill and Remy
>
> you
Hello Bill and Remy
your log4j example at new doumentation works fine. Thanx!
My fault I use the Logger tag instead the category one.
But that we can't change the Logger config at server.xml is not nice.
The only chance is, declare a Lifecycle Listner or used the Log4J MBean
direct.
Regards
Peter
B
Hello Remy,
Remy Maucherat schrieb:
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.
Hmm, is this your kind to hold a discussion? I think that my question
are qualified because I must do this things everyday.
In
>
> > 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 cus
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 o
Peter Rossbach wrote:
Also I thing the the current implementation is not compatible with all
Tomcat 5 releases
How we want migrate all the current Tomcat projects? How we made Logger
configuration
at runtime? Hmm. :-(
How about continuing using the Tomcat 5.0.x branch instead ?
About the breaka
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 .xml is not valid,
because the old logger with is defined?
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 .xml is not valid,
because the old logger with is defined?
2. How can I automatically configur
ED]>
To: "Tomcat Developers List" <[EMAIL PROTECTED]>
Sent: Thursday, June 24, 2004 11:02 AM
Subject: Re: Please describe the new Logger System at cvs head.
Hey Remy,
please look at the log4j.dtd
jakarta-log4j-1.2.8\src\java\org\apache\log4j\xml\log4j.dtd
All names from name attr
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 .xml is not valid,
because the old logger with is defined?
2. How can I automatically configure Log4J to add new cate
Bill Barker wrote:
Except that I can't see why you would want to use the
'Tomcat.[].[Catalina].[localhost].[myapp]' name except in a 'category'
element. Here, the name is defined to be CDATA so you should be fine (or it
is a log4j bug :).
Maybe Peter is stressed up because he's going to production
ssbach" <[EMAIL PROTECTED]>
To: "Tomcat Developers List" <[EMAIL PROTECTED]>
Sent: Thursday, June 24, 2004 11:02 AM
Subject: Re: Please describe the new Logger System at cvs head.
Hey Remy,
please look at the log4j.dtd
jakarta-log4j-1.2.8\src\java\org\apache\log4j\xml\lo
Hey Remy,
please look at the log4j.dtd
jakarta-log4j-1.2.8\src\java\org\apache\log4j\xml\log4j.dtd
All names from name attributes are from type "ID"
http://www.w3.org/TR/REC-xml/
XML Attribute from type ID can not have this characters "[]"
Please, accept my change or made a log4j.dtd/ XML conform
Peter Rossbach wrote:
Hello Remy,
with your Logger naming convention log4j not working
log4j:ERROR Parsing error on line 57 and column 99
log4j:ERROR Attribute value
"org.apache.catalina.core.CatalinaBase.[].[localhost
].[Catalina]" of type ID must be a name.
With this logger naming convention it
Hello Remy,
with your Logger naming convention log4j not working
log4j:ERROR Parsing error on line 57 and column 99
log4j:ERROR Attribute value
"org.apache.catalina.core.CatalinaBase.[].[localhost
].[Catalina]" of type ID must be a name.
With this logger naming convention it works fine:
org.apach
Peter Rossbach wrote:
Hello Remy,
I have made a deeper look at the current cvs logger code stage:
1) ContainerBase.getLogger()
With first getLogger call the Log was build with a strange name!
public Log getLogger() {
if (logger != null)
return (logger);
String loggerName
Hello Remy,
I have made a deeper look at the current cvs logger code stage:
1) ContainerBase.getLogger()
With first getLogger call the Log was build with a strange name!
public Log getLogger() {
if (logger != null)
return (logger);
String loggerName = null;
Contai
Hello Remy,
which logging system you used?
I thing every host and application can have there own logging devices.
My problem is:
How can I configure dymamic logging device at runtime?
For every new host or application
With the old server.xml Logger element this was easy, but now you must know
Peter Rossbach wrote:
Hello Remy,
I have problems to configure the new logger system.
Can you send a log4J example to demonstrate the new commons-log Logger
concept.
How I can configure a log4J system?
I have no success with add log4j.jar and log4j.xml to system class path
via setclasspath.bat
s
Hello Remy,
I have problems to configure the new logger system.
Can you send a log4J example to demonstrate the new commons-log Logger
concept.
How I can configure a log4J system?
I have no success with add log4j.jar and log4j.xml to system class path
via setclasspath.bat
set
CLASSPATH=%JAVA_HO
20 matches
Mail list logo
