Thanks! That was exactly what I wanted. New patch coming tomorrow.
On Oct 11, 2010, at 11:20 PM, Claus Ibsen (JIRA) wrote: > > [ > https://issues.apache.org/activemq/browse/CAMEL-3209?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=62510#action_62510 > ] > > Claus Ibsen commented on CAMEL-3209: > ------------------------------------ > > Ah great nice you are helping out. Be careful though if you help to much it > gets noticed and we will invite you in :) > > The thrown exception class should also contain the response body so end user > can access it. It may contain some additional data. > > In your patch you override the endpoint setting by the header because Camel > will return false in case the header doesn't exist. > You need to only fallback on the endpoint setting if the header is missing. > And be careful not to change the endpoint setting with the value from the > header. > As there can be exchange which has NO headers and then they must use the > correct endpoint setting, and not just the last value which was set by the > previously process message. > > You can look at camel-http which has such a feature, it may help. Also its > nice when the components act in similar ways. > >> CXF-RS - Add throwExceptionOnFailure option >> ------------------------------------------- >> >> Key: CAMEL-3209 >> URL: https://issues.apache.org/activemq/browse/CAMEL-3209 >> Project: Apache Camel >> Issue Type: New Feature >> Components: camel-cxf >> Reporter: Claus Ibsen >> >> See CAMEL-3184 >> Currently you will have to check the status code of the response if its != >> 200. > > -- > This message is automatically generated by JIRA. > - > You can reply to this email to add a comment to the issue online. > Johan Edstrom j...@opennms.org They that can give up essential liberty to purchase a little temporary safety, deserve neither liberty nor safety. Benjamin Franklin, Historical Review of Pennsylvania, 1759
