You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@camel.apache.org by "Willem Jiang (JIRA)" <ji...@apache.org> on 2009/08/07 15:20:35 UTC
[jira] Assigned: (CAMEL-1888) CamelInvocationHandler should throw
RuntimeException if possible instead of InvocationTargetException
[ https://issues.apache.org/activemq/browse/CAMEL-1888?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Willem Jiang reassigned CAMEL-1888:
-----------------------------------
Assignee: Willem Jiang
> CamelInvocationHandler should throw RuntimeException if possible instead of InvocationTargetException
> -----------------------------------------------------------------------------------------------------
>
> Key: CAMEL-1888
> URL: https://issues.apache.org/activemq/browse/CAMEL-1888
> Project: Apache Camel
> Issue Type: Improvement
> Components: camel-core, camel-spring
> Affects Versions: 2.0-M3
> Environment: XP, JDK 1.5.0_16
> Reporter: Andreas Kuhtz
> Assignee: Willem Jiang
> Fix For: 2.0.0
>
> Attachments: camel-core-1888.patch, camel-spring-1888.patch
>
>
> The CamelInvocationHandler.invoke() method should throw the RuntimeException if the fault is a RuntimeException instead of throwing an InvocationTargetException with the RuntimeException included.
> This would allow to use the @Produce to inject a direct endpoint on a pojo (that acts as a service interface) and the calling side would receive the RuntimeException instead of the UndeclaredThrowableException. With this behaviour the error handling on the calling side would be the same as if no camel route is between the caller and the called pojo.
> The attached testcase is based on the original testcase that was commited here: http://svn.apache.org/viewvc?view=rev&revision=801511
> See also http://www.nabble.com/Camel-Spring-Remoting-throwing-RuntimeException-question-td24825646.html for more info.
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.