On Tue, Dec 16, 2008 at 9:20 PM, radisb <rad...@gmail.com> wrote:
>
> I havent loooked into the code thoroughly, I guess between the two options,
> the TX policy is a better place since dead letter is supposed to be turned
> off automatically when transactions are used, or at least i think that this
> is the intended beheviour.
Well after your last post at
http://www.nabble.com/Cast-a-copy-message-to-an-endpoint-when-exception-is-thrown-td21024810s22882.html

I kinda have 2nd thoughts on configuring it on the TX. For instance
onException -> handled=true will also be bypassed for transacted
exchanges. What if you want this to be enabled for TX exchanges as
well?

So we might wanna refactor the DLC a bit to better support TX and
non-TX exchanges so it can do common stuff for both.

But for starters we might wanna have some more use-cases to use for
testing and having a solid ground before making any changes.

>
> For James suggestion: I think James essentially says that if we put this
> hidden functionality as a feature  in TX as Claus suggests, then it still
> remains what should be done when no policy is defined. The consumer
> defaulting it might be ok. But I am thinking maybe the policy should be
> mandatory when transactions are used. Maybe throw an error if a route is
> transacted without a policy.
How is this done in Spring today? It is after all the Spring TX that
is used under the covers. I think Camel should resemble what its
common sence in Spring.

>
> I must definitely look the code because maybe what i am saying makes no
> sense and also i have some other things i ve not clarified. I ll come back
> after that so i can have a more informed opinion
Yeah please dig into the codebase. The error handling is not trivial
code, so always nice with more eyes


>
> --
> View this message in context: 
> http://www.nabble.com/Please-keep-this-unintended-feature-in-camel-and-other-requests-tp21025627s22882p21040950.html
> Sent from the Camel - Users mailing list archive at Nabble.com.
>
>



-- 

/Claus Ibsen
Apache Camel Committer
Blog: http://davsclaus.blogspot.com/

Reply via email to