On Fri July 24 2009 12:20:06 pm Bruno Melloni wrote: > I have a similar situation. > > 1) Do you know why cxf would send Info/Trace messages to stderr?
I think it's a bug in how jboss has java.util.logging configured, but I'm not really sure. We just log to j.u.l and wherever it goes, it goes. > I thought > the purpose of stderr is for errors, and stdout for all other output. If > my understanding is correct (which of course is highly questionable), that > would make jBoss' behavior correct. > > 2) My application already uses log4j and its output goes to the logger just > fine. How do you tell CXF to direct its output to the jBoss logger instead > of using stderr? If there is a how-to or other documentation, can you > point me to it? There is instruction on how to get CXF to log to log4j at: http://cwiki.apache.org/CXF20DOC/debugging.html Dan > > Thanks. > > -----Original Message----- > From: Andrew Dinn [mailto:[email protected]] > Sent: Friday, July 24, 2009 3:02 AM > To: [email protected] > Subject: Re: Errors while deploying Service on JBoss > > <snip> > Those are info/trace messages, not error messages. You are seeing them > tagged as errors because the JBoss logger tags anything written to > stderr with the prefix ERROR [STDERR]. > > Are you using the CXF stack underneath JBossWS or by embedding the CXF > jars in your web application? It looks to me like the latter. If so > then you need to change your app so that its output is explicitly > directed to the JBoss logger rather than via stderr. Alternatively, you > can just ignore the ERROR [STDERR] at the front and check the message > for an ERROR, WARN or INFO tag (clearly, looking at message 2, CXF does > not always append an INFO tag so you may need to apply some discretion). > > regards, > > > Andrew Dinn > ----------- -- Daniel Kulp [email protected] http://www.dankulp.com/blog
