camel-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Claus Ibsen (JIRA)" <>
Subject [jira] Commented: (CAMEL-585) JMS Component - Look at Bruces investigations (message transfer using JMS and exceptions)
Date Sun, 14 Sep 2008 11:36:56 GMT


Claus Ibsen commented on CAMEL-585:

The FAULT stuff is now in place. However the exception needs more consideration and feedback.

Currently if the exchange could not be proceseed it will throw a runtime exception that Spring
will catch and do a rollback on the TX. This is something that end-users might want to happend
vs. sending a serialized stacktrace back over the wire.

I think we need a flag to set what behavior end-users want.

Feedback welcome

> JMS Component - Look at Bruces investigations (message transfer using JMS and exceptions)
> -----------------------------------------------------------------------------------------
>                 Key: CAMEL-585
>                 URL:
>             Project: Apache Camel
>          Issue Type: Task
>          Components: camel-jms
>    Affects Versions: 1.3.0, 1.4.0
>            Reporter: Claus Ibsen
>            Assignee: Claus Ibsen
>             Fix For: 1.5.0
> Bruce Elmore have investigated and do think that Camel has a bug in the JMS compoenent
regarding how exceptions is received from the JMS Producer (when receiving the reply).
> If the reply was a thrown exception from the other part, this is not currently set as
an exception on the build Exchange but on the body as is.
> Pitfall: If an exception should be deserialized and set as an exception object on the
created exception there could be problems with that the exception class does not exists on
the receive side.
> Would be great to get James and other core comitters opinion on this matter, as it's
maybe also a more general pattern for other components as well.
> This ticket is created to not forget about the postings on the user forum:
> nabble: (Handle Bean Exception)

This message is automatically generated by JIRA.
You can reply to this email to add a comment to the issue online.

View raw message