Ole,
XSLT is one solution. Have a look at org/apache/log4j/xml/tentative.xml for an example
of a style sheet. Cheers, Ceki
At 17:34 11.05.2001 +0200, you wrote:
>Hi!
>
>I am a very happy user of log4j.
>I am looking for a viewer for the XML log files generated by the XMLLayout.
>Something tra
Henrique,
Have a look at log4j.dtd. That should put you on the right track. Ceki
At 15:57 11.05.2001 -0300, you wrote:
>Hi folks,
>
>How do I disable all logging (disable log4j) on the XML file?
>
>A.F.A.I.K. in the PropertyConfigurator "way", I should use log4j.disable=3DFATAL, but
>I have
Hi,
First of all, let me say thanks to all the developers for making such a
great product available. I am currently trying to resolve an issue related
to reading the log4j configuration from an xml file contained in a WAR. I
have browsed through the archives and found some seemly related issues
Title: disable log4j on the XML file
Hi folks,
How do I disable all logging (disable log4j) on the XML file?
A.F.A.I.K. in the PropertyConfigurator "way", I should use log4j.disable=3DFATAL, but I have no idea what could be XML (DOMConfigurator) equivalent entry...
Thanks,
Henrique
===
Hi!
I am a very happy user of log4j.
I am looking for a viewer for the XML log files generated by the XMLLayout.
Something transforming the XML to HTML would be fine to.
But I would need the source code since I made some extensions to the
XMLLayout (but didn't adjust the DTD so far).
This is aswe
Hello,
I am hoping that this is an appropriate forum.
I am writing a bean for logging (using log4j), to be used by other beans
(under JBoss).
I would like to do the following, but am unsure about where and how to
define the log4j properties file as an EJB Container resource:
Make a properties-fi
Aaron,
Although I do not think it could be the cause, could you please try to see if you have
the same problem in 1.1b7?
It seems to me that the parser is not handing out the elements in the order they
appeared in the document. Which version of Xerces is this by the way? Thanks, Ceki
At 17
Hi, I have a problem with XML configuration using v1.0.4.
I'm trying to set up a very simple appender on root, using the sample XML files
as a model:
I consistently receive the output:
log4j: root priority set to DEBUG
log4j:ERROR No appender n
Thilo,
You do no need the hashtable in CategoryManager. One of the important benefits of
log4j is that it manages the category namespace for you automatically. Have a look at
Category.getInstance() and Hierarchy.getInstance() to see what I mean. Ceki
At 15:37 11.05.2001 +0200, you wrote:
>Hi
Hi anybody,
I attached a solution how to handle the need of different
categories/appenders for threads, applications, sessions or what else. The
solution consists of two classes:
1) CategoryManager.java
2) TestCategoryManager.java
1) manages all the categories in a hashtable. The generel proced
Hello,
I'm an happy user of Log4J. I didn't understand if in new 1.6b version
is avaible a "Priority Appender". I mean: an appender able to dispatch
received messages to several destinations, one per each priority level.
I already have developed classes to do that (one generic and one child,
sp
At 12:11 11.05.2001 +0200, you wrote:
>Dear Ceki,
>
>thank you for your hint.
>
>I am not sure a understand your question but it is the XML parser that
>creates the DOM tree. The parser is invoked in the doConfigure(InputStream
>input, Hierarchy hierarchy) method in DOMConfigurator.
>These are the
Hi!
I have just started using log4j. I plan to use it in a web application.
My question is do I have to create new instances and set the
configuration each time I access it from different places in my web
application? For example, I would access it from the jsp page, servlet,
beans and other
Dear Ceki,
thank you for your hint.
I am not sure a understand your question but it is the XML parser that
creates the DOM tree. The parser is invoked in the doConfigure(InputStream
input, Hierarchy hierarchy) method in DOMConfigurator.
These are the lines that are perhaps the most relevant.
At 11:31 11.05.2001 +0200, you wrote:
>I had a look at the class DOMConfigurator searching where the data for the
>DOM object is held, but I only recognized that a hashtable of appenders is
>build up.
>
>How can I access the DOM tree (root element)? As written in the DTD the
>element "configurat
I had a look at the class DOMConfigurator searching where the data for the
DOM object is held, but I only recognized that a hashtable of appenders is
build up.
How can I access the DOM tree (root element)? As written in the DTD the
element "configuration" should be the root element.
I need the
Dear Robert, dear Jeff,
I read your conversation. To my opinion the workaround (removing the doctype
comment which refers to the DTD) has the disadvantage that your XML file is
"well formed", but (possibly) not valid!
I think that the problem is caused by the URI/namespace:
http://jakarta.apach
17 matches
Mail list logo