RE: Problems logging from a Junit test

> -----Original Message-----
> From: David Durham [mailto:david.durham1 <at> scott.af.mil] 
> Sent: Tuesday, August 31, 2004 11:28 PM
> To: Log4J Users List
> Subject: Re: Problems logging from a Junit test
> 
> ... [SNIP]...
> and it now looks for log4j.properties in .../WEB-INF/classes 
> before looking through the various jars (I'm using JDK 
> 1.4.2_03).  Presumably all classloaders will search for 
> resources similarly.
> 
> BTW, the offending Jar (at least the first one I found) was 
> xdoclet-1.2.1.  Why would they put a log4j.properties file in 
> that jar?  
> I guess that's a question for the xdoclet list.

I'm off topic here but...
Last week I was trying to use the latest Jetty 5.0RC2 (that for the
first time it uses commos-logging) inside my JBuilder, I was always
getting:

> org.apache.commons.logging.LogConfigurationException: Class 
> org.apache.commons.logging.impl.Log4JLogger does not
> implement Log 	at 
> org.apache.commons.logging.impl.LogFactoryImpl.newInstance(Log
> FactoryImpl.java:532)

Outside JBuilder everything was fine but within it in some way his

Re: maintaining the Frequently Asked Questions

As no one is currently maintaining the log4j wiki, it is not really
helping us to create better documentation. On the contrary, it mostly
increases the noise level causing damage to the image of the project.

To give you an example, the main log4j wiki page
http://wiki.apache.org/logging-log4j/Log4JProjectPages has been
vandalized over 2 months ago and no one has corrected the problem nor
complained about it.

As far as I can tell, the log4j wiki is a failed experiment. Instead
of replicating the existing documentation, the log4j wiki should be
abandoned, unless we find a volunteer to maintain it.

Do we have such a volunteer?

At 02:55 PM 8/31/2004, Jim Moore wrote:
>Is there any way for users to help maintain the FAQ for log4j?

Yes, there is. You can submit a patch against

http://logging.apache.org/log4j/docs/faq.html

the source file is at

logging-log4j/src/xdocs/faq.xml

where log4j-log4j is the directory where you checked out the
logging-log4j module.

Re: maintaining the Frequently Asked Questions

Not about the wiki thing : I am currently traducting
the short log4j manual in french (spanish and german
are already available)

As I do this in my spare time (at work obviously), it
takes quite a long ...

	

	
		
Vous manquez d’espace pour stocker vos mails ? 
Yahoo! Mail vous offre GRATUITEMENT 100 Mo !
Créez votre Yahoo! Mail sur http://fr.benefits.yahoo.com/

Le nouveau Yahoo! Messenger est arrivé ! Découvrez toutes les nouveautés pour dialoguer
instantanément avec vos amis. A télécharger gratuitement sur http://fr.messenger.yahoo.com

Re: maintaining the Frequently Asked Questions

Ionel,

Do you have a preliminary version available somewhere?

At 12:51 PM 9/1/2004, Ionel GARDAIS wrote:
>Not about the wiki thing : I am currently traducting
>the short log4j manual in french (spanish and german
>are already available)
>
>As I do this in my spare time (at work obviously), it
>takes quite a long ...
>
>
>

--

-- 
Ceki Gülcü

      For log4j documentation consider "The complete log4j manual"
      ISBN: 2970036908 http://www.qos.ch/shop/products/clm_t.jsp  

Re: maintaining the Frequently Asked Questions

not yet.
As I started this a few days ago, only the intro part
is already traducted.

i did not traduct the Apache licence stuff (should I
?) and the Kernigan/Pike quote.

FYI, I attach the html file.

Layout is the same as the original file.

	

	
		
Vous manquez d’espace pour stocker vos mails ? 
Yahoo! Mail vous offre GRATUITEMENT 100 Mo !
Créez votre Yahoo! Mail sur http://fr.benefits.yahoo.com/

Le nouveau Yahoo! Messenger est arrivé ! Découvrez toutes les nouveautés pour dialoguer
instantanément avec vos amis. A télécharger gratuitement sur http://fr.messenger.yahoo.com

---------------------------------------------------------------------
To unsubscribe, e-mail: log4j-user-unsubscribe <at> logging.apache.org
For additional commands, e-mail: log4j-user-help <at> logging.apache.org

Re: maintaining the Frequently Asked Questions

A wiki needs to be easily editable, or it isn't a wiki.

The entire site is immutable, and clicking on the edit button says
"You are not allowed to edit this page."  No reason why, no suggestion
on how that might be changed, no nothing -- just that I'm not allowed
to edit it.

People can hardly be faulted for not maintaining something that they
can't maintain.  And since those in charge of the wiki's content
obviously want it frozen, what's the point in complaining about it? 
The appearance is that those in charge WANT it to say that "Andreav is
a fast and flexible framework" because they're the only ones that can
(at least at this time) make that kind of edit.  (Or people just
didn't notice that it said "Andreav"... I had to read the page a
couple of times before my brain didn't automatically substitute
"log4j" there.)

Having A volunteer maintain it goes against the point of a wiki.  The
point is that the community maintains it.  Right now that's not
happening because it's not easy to do.

It may be that it's a problem with bad user-interface design -- maybe
you CAN edit pages, but you need to log in first.  But there's no link
that says "login" or "registration", and the error message doesn't say
that it's even necessary.  It's hardly surprising that the designers
of MoinMoin would overlook that since having to jump through hoops to
edit a wiki largely violates the spirit, but it's still an issue.

"You can submit a patch against..."

Re: maintaining the Frequently Asked Questions

At 05:03 PM 9/1/2004, you wrote:
>A wiki needs to be easily editable, or it isn't a wiki.
>
>The entire site is immutable, and clicking on the edit button says
>"You are not allowed to edit this page."  No reason why, no suggestion
>on how that might be changed, no nothing -- just that I'm not allowed
>to edit it.

You have to be logged in to edit the pages. Otherwise, the page is marked 
as immutable. It seems that *all* Apache wiki pages exhibit this behavior.

>People can hardly be faulted for not maintaining something that they
>can't maintain.

Correct.

>And since those in charge of the wiki's content
>obviously want it frozen, what's the point in complaining about it?

That is not a correct characterization because the pages become editable as 
soon as you log in as anybody. You don't need special privs to edit the pages.

>The appearance is that those in charge WANT it to say that "Andreav is
>a fast and flexible framework" because they're the only ones that can
>(at least at this time) make that kind of edit.  (Or people just
>didn't notice that it said "Andreav"... I had to read the page a
>couple of times before my brain didn't automatically substitute
>"log4j" there.)

>Having A volunteer maintain it goes against the point of a wiki.  The

RE: maintaining the Frequently Asked Questions

>But having three FAQs (faq.xml, the old wiki and the moinmoin one) is
>confusing and aggravating.  Two of them need to be killed, and the
>remaining one easily maintainable.

+1

---------------------------------------------------------------------
To unsubscribe, e-mail: log4j-user-unsubscribe <at> logging.apache.org
For additional commands, e-mail: log4j-user-help <at> logging.apache.org

RE: Class loading issues using WLS 8.1?

Apologies for joining this thread so late in the discussion...

Can you detail how you are packaging up your EARs (I seem to recall they
were EARs as opposed to WARs)... If you have not tried it, you might see if
moving your jars in the EAR into the WLS proprietary APP-INF/lib dir
(exactly akin to WEB-INF/ in WARs) and see if that helps any.

-d

-----Original Message-----
From: Jacob Kjome [mailto:hoju <at> visi.com] 
Sent: Monday, August 30, 2004 1:47 PM
To: Log4J Users List
Subject: RE: Class loading issues using WLS 8.1?

One other thing to remember is not to put endorsed libraries in WEB-INF/lib.

That is, libraries that are part of the JDK or J2EE.  I believe Tomcat
solves this by actively not loading endorsed packages in WEB-INF/lib.
However, I wouldn't count on other appservers doing the same.

Rules of thumb...

1.  Never put an XML parser in WEB-INF/lib.  Put it in the appserver's
classpath.  You should be using the standard API's anyway and shouldn't need
to worry about which implementation you are using.

2.  Never put stuff like activation.jar, JDBC drivers, etc... in
WEB-INF/lib. 
These are endorsed packages and should be loaded by the application server.

[Chainsaw]: Drag & Drop support

Hi All,
I have added Drag & Drop support to Chainsaw v2.  You can now DnD log files
onto the tabbed pane and Chainsaw will load them.  
Webstart version updated:
http://logging.apache.org/log4j/docs/webstart/chainsaw/chainsawWebStart.jnlp
Standalone bundle updated: 
http://logging.apache.org/log4j/docs/webstart/chainsaw/chainsaw-bundle.zip
cheers,
Paul Smith