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:[EMAIL PROTECTED] Sent: Thursday, April 24, 2008 6:43 AM To: [email protected] 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 > > >
