On Tue, Nov 8, 2011 at 7:41 PM, Jean-Baptiste Onofré j...@nanthrax.net wrote:
Hi Claus,
It's interesting, and, definitely, it makes sense.
Regarding the implementation, I remember that Christian Schneider talked
about a change in CXF to enhance the logging. If I remember well, he
talked
Sounds good.
I even have a more radical idea. I just recently tweaked the CXF
LoggingFeature. So it now writes to different logger categories for each
service.
So we might also think about doing logging all the time and only enable
/ disable it through the logger config.
The reason why I
Hi
When working with camel-cxf, you can get pretty fast setup with the
Camel cxfEndpoint element as shown:
For example to call the famous weather web service
cxf:cxfEndpoint id=weatherWebService
address=http://www.webservicex.net/globalweather.asmx;
Hi Claus,
CXF has the log feature can avoid us to configure lots of interceptors.
but it could be more handy if we add an attribute on the cxfEndpoint.
+1 for this idea.
On Tue Nov 8 18:36:27 2011, Claus Ibsen wrote:
Hi
When working with camel-cxf, you can get pretty fast setup with the
Hi,
Sounds very convenient.
Special care must be taken when dataFormat=MESSAGE
(http://camel.apache.org/cxf.html#CXF-HowtoenableCXF%2527sLoggingOutInterce
ptorinMESSAGEmode).
Shall we also allow the user to specify the limit, as per the
Logging*Interceptor(int) constructors? Otherwise, it
Hi,
I like this idea, too. However, it should be possible to specify a custom
logging interceptor if logging=true that overrides the default logging
interceptor ... but I think that's what was already in your minds ;-)
Regards,
Andi
--
View this message in context:
2011/11/8 Raúl Kripalani r...@fusesource.com:
Hi,
Sounds very convenient.
Special care must be taken when dataFormat=MESSAGE
(http://camel.apache.org/cxf.html#CXF-HowtoenableCXF%2527sLoggingOutInterce
ptorinMESSAGEmode).
Shall we also allow the user to specify the limit, as per the
On Tue, Nov 8, 2011 at 11:59 AM, Andreas Kuhtz andreas.ku...@atos.net wrote:
Hi,
I like this idea, too. However, it should be possible to specify a custom
logging interceptor if logging=true that overrides the default logging
interceptor ... but I think that's what was already in your minds
Exactly, that's the special case I'm referring to.
The LoggingOutInterceptor attaches itself to the PRE_STREAM phase of the
interception chain. Apparently, this phase is not executed when
dataFormat=MESSAGE on the CXF endpoint.
So by passing the string write to the constructor, you tell the
On 11/8/11 6:51 PM, Raúl Kripalani wrote:
Hi,
Sounds very convenient.
Special care must be taken when dataFormat=MESSAGE
(http://camel.apache.org/cxf.html#CXF-HowtoenableCXF%2527sLoggingOutInterce
ptorinMESSAGEmode).
Shall we also allow the user to specify the limit, as per the
I just checked the CxfEndpoint code and find there is
loggingFeatureEnabled option, we just need to make it available in
cxfEndpoint attribute.
BTW, I'm planing to add the loggingLimit option at the same time.
On 11/8/11 6:36 PM, Claus Ibsen wrote:
Hi
When working with camel-cxf, you can get
The attribute (loggingFeatureEnabled) already exists. in camel-cxf
endpoint Please check out http://camel.apache.org/cxf.html.
On 11/08/2011 05:43 AM, Willem Jiang wrote:
Hi Claus,
CXF has the log feature can avoid us to configure lots of
interceptors. but it could be more handy if we add
Hi Claus,
It's interesting, and, definitely, it makes sense.
Regarding the implementation, I remember that Christian Schneider talked
about a change in CXF to enhance the logging. If I remember well, he
talked about shipping logging in in/out by default, and enabling it by
configuration (if
13 matches
Mail list logo
