It's entirely at runtime. And we do it all the time. I'm perplexed.

I could also give you a recipe for how to make an explicit call for the
purpose.


On Fri, Sep 19, 2008 at 3:34 PM, Hans Loeblich <[EMAIL PROTECTED]
> wrote:

> I don't really see the difference, since the jar is on the classpath too,
> but I went ahead and tried your suggestion.
> So I've I tried adding to jar file, adding direclty to classpath as you
> suggested, and even supplying vm arguments, but still none of these make any
> difference.  Is this part of the wsdl2java step, or just when running the
> generated code?  Either way, I tried it on both steps.  I just don't get it.
>
> Hans
>
> ----- Original Message -----
> From: "Benson Margulies" <[EMAIL PROTECTED]>
> To: [email protected]
> Sent: Wednesday, September 17, 2008 5:26:17 PM GMT -06:00 US/Canada Central
> Subject: Re: log4j and logging soap requests
>
> Don't modify the CXF jar file. Just add a file at that path to your
> classpath. That should do it.
>
> For logging of messages:
>
> http://cwiki.apache.org/CXF20DOC/debugging.html has an explanation.
> The interceptors log all of the messages when enabled.
>
>
> On Wed, Sep 17, 2008 at 6:10 PM, Hans Loeblich
> <[EMAIL PROTECTED]> wrote:
> > I have two issues currently related to logging.
> >
> > First I would like to be able to log the SOAP request that is being
> generated on the client side.  I just have no what class I would need to add
> a logging statement to, or if anything like this can be setup through
> configuration files, etc.
> >
> > My second issue is that I would like to use log4j for logging.  I tried
> following the instructions from this page:
> >
> http://www.techper.net/2008/01/30/configuring-cxf-logging-to-go-through-log4j/
> >
> > I inserted META-INF/cxf/org.apache.cxf.Logger into my cxf-2.1.2.jar file,
> with just a single line in the file containing the text
> "org.apache.cxf.common.logging.Log4jLogger".  But it did not seem to make
> any difference.  Am I doing something wrong here?
> >
> > Thank you,
> > Hans Loeblich
> >
>

Reply via email to