Wouldn't it make sense to use commons logging? I implemented it on some code recently and it seems a bit of a no brainer...
John Baker -- Web SSO IT Infrastructure Deutsche Bank London URL: http://websso.cto.gt.intranet.db.com Daniel Kulp <[EMAIL PROTECTED]> 06/03/2008 15:12 Please respond to [email protected] To [email protected] cc John-M Baker/ext/[EMAIL PROTECTED] Subject Re: CXF logging On Thursday 06 March 2008, John-M Baker wrote: > So does it not use log4j by default? Or commons logging, rather? No... commons-logging is there cause a couple of dependencies require it (spring, maybe jetty). By default, it's straight java.util.logging. Dan > > John Baker > -- > Web SSO > IT Infrastructure > Deutsche Bank London > > URL: http://websso.cto.gt.intranet.db.com > > > > > "David Castañeda" <[EMAIL PROTECTED]> > 06/03/2008 14:58 > Please respond to > [email protected] > > > To > [email protected] > cc > > Subject > Re: CXF logging > > > > > > > that's what I do, because I use Log4J ... to the JVM, pass this > parameter. and configure log4j > > -Dorg.apache.cxf.Logger=org.apache.cxf.common.logging.Log4jLogger > > > But what you really need is an interceptor, see the docs and samples > and search for LogInInterceptor and LogOutInterceptor. > > On Thu, Mar 6, 2008 at 9:50 AM, John-M Baker <[EMAIL PROTECTED]> wrote: > > Hi, > > > > What's the best way to turn on debug logging? I'd like to see what > > XML > > is > > > being sent from the client and I'm sure that'll be in the debug > > (well, > > I > > > hope it is!). I tried a simple log4j.xml file but that iddn't seem > > to work. > > > > Thanks, > > > > > > John Baker > > -- > > Web SSO > > IT Infrastructure > > Deutsche Bank London > > > > URL: http://websso.cto.gt.intranet.db.com > > > > > > --- > > > > This e-mail may contain confidential and/or privileged information. > > If > > you are not the intended recipient (or have received this e-mail in > error) please notify the sender immediately and delete this e-mail. > Any unauthorized copying, disclosure or distribution of the material > in this e-mail is strictly forbidden. > > > Please refer to http://www.db.com/en/content/eu_disclosures.htm for > > additional EU corporate and regulatory disclosures. -- J. Daniel Kulp Principal Engineer, IONA [EMAIL PROTECTED] http://www.dankulp.com/blog --- This e-mail may contain confidential and/or privileged information. If you are not the intended recipient (or have received this e-mail in error) please notify the sender immediately and delete this e-mail. Any unauthorized copying, disclosure or distribution of the material in this e-mail is strictly forbidden. Please refer to http://www.db.com/en/content/eu_disclosures.htm for additional EU corporate and regulatory disclosures.
