[
https://issues.apache.org/activemq/browse/CAMEL-2613?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=58676#action_58676
]
James Strachan commented on CAMEL-2613:
---------------------------------------
my worry is really folks losing exceptions without really knowing about it.
Certainly we should only support this for void methods with no checked
exceptions. Though if the method is invoking lots of spring stuff, which tends
to use runtime exceptions (or scala code which does the same) - its very easy
to lose exceptions.
We need to make a massive error message if a runtime exception is thrown and
the method is invoked async so folks are really aware.
So long as the default is to only do async when @InOnly is there, I'm happy.
Having an option to override this (for example when using legacy code) is fine,
so long as users understand the big risk they are taking
> CamelProxy - Add option to treat void methods as InOnly for fire and forget
> style messaging
> -------------------------------------------------------------------------------------------
>
> Key: CAMEL-2613
> URL: https://issues.apache.org/activemq/browse/CAMEL-2613
> Project: Apache Camel
> Issue Type: Improvement
> Components: camel-core
> Reporter: Claus Ibsen
> Assignee: Claus Ibsen
> Priority: Minor
> Fix For: 2.3.0
>
>
> By default Camel Proxy is always {{InOut}} unless you set some specific
> @Pattern annotation such as @InOnly.
> We should add an option to <camelProxy> so you can let {{void}} methods be
> {{InOnly}} and the others {{InOut}}.
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
