[
https://issues.apache.org/activemq/browse/CAMEL-810?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=44922#action_44922
]
James Strachan commented on CAMEL-810:
--------------------------------------
Agreed. I've been hacking something along those lines.
Am thinking of @InOnly which is only ExchangePattern.InOnly and @InOut which is
only ExchangePattern.InOut then allowing @Pattern(ExchangePattern.RobustInOut)
for any other non-common exchange patterns.
While users might not use @Pattern directly - I was thinking of using this
annotation to annotate the annotations themselves. e.g. rather than knowing
about the special @InOut or @InOnly annotations - we'd just look for
annotations which are annotated with @Pattern to specify the pattern. That way
folks who already have created, say, an @Async annotation could just add
@Pattern(ExchangePattern.InOnly) so camel would auto-recognise it as being a
oneway rather than request reply operation.
> support for asynchronous invocation in Spring Remoting
> ------------------------------------------------------
>
> Key: CAMEL-810
> URL: https://issues.apache.org/activemq/browse/CAMEL-810
> Project: Apache Camel
> Issue Type: New Feature
> Components: camel-spring
> Reporter: James Strachan
> Assignee: James Strachan
> Fix For: 1.5.0
>
>
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
