Just one comment for the FaultMessage.
If we want to return a soap fault message in camel-cxf endpoint , we
need to set the exchange's FaultMessage with the soap fault message and
not the exchange's Exception to avoid the deadLetterChannel handling.
Here is a unit test[1] to show it.
[1]
https://svn.apache.org/repos/asf/activemq/camel/trunk/components/camel-cxf/src/test/java/org/apache/camel/component/cxf/CxfCustomizedExceptionTest.java
Willem
Claus Ibsen wrote:
Hi
Oh I can see I hit a nerve here having read the entire conversation. I like the
chair analogy ;)
I do think it is important that we pick up this ball now that we are designing for Camel 2.0. If we don't start doing something about it now we wont make it for Camel 2.0 and we have to "wait" until Camel 3.0.
I do feel Roman's pain and point of view of the current model, so we are two in
that direction ;)
Med venlig hilsen
Claus Ibsen
......................................
Silverbullet
Skovsgårdsvænget 21
8362 Hørning
Tlf. +45 2962 7576
Web: www.silverbullet.dk
-----Original Message-----
From: Roman Kalukiewicz [mailto:[EMAIL PROTECTED]
Sent: 14. september 2008 14:18
To: [email protected]
Subject: Re: Camel 2.0 - FAULT message, do we need it?
Just to remind an old discussion about in/out/fault
http://www.nabble.com/in-out-fault-messages-discussion-to14170013s22882.html#a14170013
I still believe that we could get rid of fault AND out message at all,
but even removing fault only has mine +1
Roman
2008/9/14 Claus Ibsen <[EMAIL PROTECTED]>:
Hi
Just a quick mail to get the discussion rolling.
I think we should @deprecated exchange.fault in Camel 1.5 and remove it in
Camel 2.0.
It is a confusing concept that isn't used much, and many components doesn't
handle the FAULT message. For instance it was missing in camel-jms a very
central component.
Med venlig hilsen
Claus Ibsen
......................................
Silverbullet
Skovsgårdsvænget 21
8362 Hørning
Tlf. +45 2962 7576
Web: www.silverbullet.dk
