You are viewing a plain text version of this content. The canonical link for it is here.
Posted to users@cxf.apache.org by harbhanu <ha...@huawei.com> on 2008/04/23 12:05:51 UTC
Using logger !
Hi,
As per the documentation for CXF, incase the logger is associated with the
SEI , using annotations, it enables logging for both client-server.
Otherwise if it's done only for SEI Implementation, then it enable only
server side logging.
But to my surprise, once I have specified the handler to console in
"logging. Properties" file it logs for both client and server.
For server there is a visible difference when I associate logging
interceptors, but there is NO change for client.
Does it mean that specifying "loggin.properties" file by itself enables some
amount of logging??
I think there are some subtle points regarding logging that I am missing.
Any comments ?
Thanks N Regards,
Harbhanu
PS: I have tried this for code generated using Wsdl2Java and executed using
the generated build.xml
RE: Using logger !
Posted by Per Olesen <po...@nordija.com>.
Hi Harbhanu,
Previously, I have done some investigation on cxf logging myself, and have
documented it here:
http://www.techper.net/2008/01/30/viewing-inbound-and-outbound-messages-in-cxf/
http://www.techper.net/2008/01/30/configuring-cxf-logging-to-go-through-log4j/
http://www.techper.net/2008/02/28/making-cxf-log-runtimeexceptions-from-server-implementations/
Maybe the information on the links can help you. I have no information
about the interceptor annotations, but on how to spring-configure the
interceptors and enable the correct logging levels.
Hope it can be of any help!
/Per
harbhanu wrote:
>
> I wanted to have logging only with the client and for that I added the
> similar annotation in client code i.e. using @In & @OutInterceptors.
>
> So, I thin that this is surely something to do with usage... Pls. clarify
> as
> to how I can add interceptors only with client.
>
> Also, thanks for the prompt and useful reply.
>
> Regards,
> Harbhanu
>
> -----Original Message-----
> From: Willem Jiang [mailto:willem.jiang@gmail.com]
> Sent: Thursday, April 24, 2008 6:43 AM
> To: cxf-user@incubator.apache.org
> Subject: Re: Using logger !
>
> I think you are talking about two difference thing.
> One is the Logging{In|Out}Interceptor which logs the request and
> response message and it could be configured with annotation.
>
> The other is the logging.Properties file which could configure the j.u.l
> 's logging level.
>
> Since the logging interceptor's default logging level is INFO, you could
> see request and response message without change the logging.Properties
> file (The default j.u.l logging level is INFO).
>
> You said you can't get the client side request and response message from
> the log. It might be the CXF's bug. Could you show me the Client
> creating code?
>
> BTW, you could also find some CXF logging information here [1]
> [1]http://cwiki.apache.org/CXF20DOC/debugging.html
>
> Willem
>
>
> harbhanu wrote:
>> Hi,
>>
>> As per the documentation for CXF, incase the logger is associated with
>> the
>> SEI , using annotations, it enables logging for both client-server.
>>
>> Otherwise if it's done only for SEI Implementation, then it enable only
>> server side logging.
>>
>>
>>
>> But to my surprise, once I have specified the handler to console in
>> "logging. Properties" file it logs for both client and server.
>>
>> For server there is a visible difference when I associate logging
>> interceptors, but there is NO change for client.
>>
>>
>>
>> Does it mean that specifying "loggin.properties" file by itself enables
> some
>> amount of logging??
>>
>>
>>
>> I think there are some subtle points regarding logging that I am
>> missing.
>> Any comments ?
>>
>>
>>
>> Thanks N Regards,
>>
>> Harbhanu
>>
>> PS: I have tried this for code generated using Wsdl2Java and executed
> using
>> the generated build.xml
>>
>>
>>
>
>
--
Per Olesen @ Nordija A/S - www.nordija.com - main#: +45 70 20 25 10
email: polesen@nordija.com - cell#: +45 23 38 95 81
RE: Using logger !
Posted by Glen Mazza <gl...@verizon.net>.
Here's our guide: http://cwiki.apache.org/CXF20DOC/debugging.html
HTH,
Glen
2008-04-24 harbhanu wrote:
> I wanted to have logging only with the client and for that I added the
> similar annotation in client code i.e. using @In & @OutInterceptors.
>
> So, I thin that this is surely something to do with usage... Pls. clarify as
> to how I can add interceptors only with client.
>
> Also, thanks for the prompt and useful reply.
>
> Regards,
> Harbhanu
>
> -----Original Message-----
> From: Willem Jiang [mailto:willem.jiang@gmail.com]
> Sent: Thursday, April 24, 2008 6:43 AM
> To: cxf-user@incubator.apache.org
> Subject: Re: Using logger !
>
> I think you are talking about two difference thing.
> One is the Logging{In|Out}Interceptor which logs the request and
> response message and it could be configured with annotation.
>
> The other is the logging.Properties file which could configure the j.u.l
> 's logging level.
>
> Since the logging interceptor's default logging level is INFO, you could
> see request and response message without change the logging.Properties
> file (The default j.u.l logging level is INFO).
>
> You said you can't get the client side request and response message from
> the log. It might be the CXF's bug. Could you show me the Client
> creating code?
>
> BTW, you could also find some CXF logging information here [1]
> [1]http://cwiki.apache.org/CXF20DOC/debugging.html
>
> Willem
>
>
> harbhanu wrote:
> > Hi,
> >
> > As per the documentation for CXF, incase the logger is associated with the
> > SEI , using annotations, it enables logging for both client-server.
> >
> > Otherwise if it's done only for SEI Implementation, then it enable only
> > server side logging.
> >
> >
> >
> > But to my surprise, once I have specified the handler to console in
> > "logging. Properties" file it logs for both client and server.
> >
> > For server there is a visible difference when I associate logging
> > interceptors, but there is NO change for client.
> >
> >
> >
> > Does it mean that specifying "loggin.properties" file by itself enables
> some
> > amount of logging??
> >
> >
> >
> > I think there are some subtle points regarding logging that I am missing.
> > Any comments ?
> >
> >
> >
> > Thanks N Regards,
> >
> > Harbhanu
> >
> > PS: I have tried this for code generated using Wsdl2Java and executed
> using
> > the generated build.xml
> >
> >
> >
>
RE: Using logger !
Posted by harbhanu <ha...@huawei.com>.
I wanted to have logging only with the client and for that I added the
similar annotation in client code i.e. using @In & @OutInterceptors.
So, I thin that this is surely something to do with usage... Pls. clarify as
to how I can add interceptors only with client.
Also, thanks for the prompt and useful reply.
Regards,
Harbhanu
-----Original Message-----
From: Willem Jiang [mailto:willem.jiang@gmail.com]
Sent: Thursday, April 24, 2008 6:43 AM
To: cxf-user@incubator.apache.org
Subject: Re: Using logger !
I think you are talking about two difference thing.
One is the Logging{In|Out}Interceptor which logs the request and
response message and it could be configured with annotation.
The other is the logging.Properties file which could configure the j.u.l
's logging level.
Since the logging interceptor's default logging level is INFO, you could
see request and response message without change the logging.Properties
file (The default j.u.l logging level is INFO).
You said you can't get the client side request and response message from
the log. It might be the CXF's bug. Could you show me the Client
creating code?
BTW, you could also find some CXF logging information here [1]
[1]http://cwiki.apache.org/CXF20DOC/debugging.html
Willem
harbhanu wrote:
> Hi,
>
> As per the documentation for CXF, incase the logger is associated with the
> SEI , using annotations, it enables logging for both client-server.
>
> Otherwise if it's done only for SEI Implementation, then it enable only
> server side logging.
>
>
>
> But to my surprise, once I have specified the handler to console in
> "logging. Properties" file it logs for both client and server.
>
> For server there is a visible difference when I associate logging
> interceptors, but there is NO change for client.
>
>
>
> Does it mean that specifying "loggin.properties" file by itself enables
some
> amount of logging??
>
>
>
> I think there are some subtle points regarding logging that I am missing.
> Any comments ?
>
>
>
> Thanks N Regards,
>
> Harbhanu
>
> PS: I have tried this for code generated using Wsdl2Java and executed
using
> the generated build.xml
>
>
>
Re: Using logger !
Posted by Willem Jiang <wi...@gmail.com>.
I think you are talking about two difference thing.
One is the Logging{In|Out}Interceptor which logs the request and
response message and it could be configured with annotation.
The other is the logging.Properties file which could configure the j.u.l
's logging level.
Since the logging interceptor's default logging level is INFO, you could
see request and response message without change the logging.Properties
file (The default j.u.l logging level is INFO).
You said you can't get the client side request and response message from
the log. It might be the CXF's bug. Could you show me the Client
creating code?
BTW, you could also find some CXF logging information here [1]
[1]http://cwiki.apache.org/CXF20DOC/debugging.html
Willem
harbhanu wrote:
> Hi,
>
> As per the documentation for CXF, incase the logger is associated with the
> SEI , using annotations, it enables logging for both client-server.
>
> Otherwise if it's done only for SEI Implementation, then it enable only
> server side logging.
>
>
>
> But to my surprise, once I have specified the handler to console in
> "logging. Properties" file it logs for both client and server.
>
> For server there is a visible difference when I associate logging
> interceptors, but there is NO change for client.
>
>
>
> Does it mean that specifying "loggin.properties" file by itself enables some
> amount of logging??
>
>
>
> I think there are some subtle points regarding logging that I am missing.
> Any comments ?
>
>
>
> Thanks N Regards,
>
> Harbhanu
>
> PS: I have tried this for code generated using Wsdl2Java and executed using
> the generated build.xml
>
>
>