[
https://issues.apache.org/activemq/browse/CAMEL-810?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=44911#action_44911
]
James Strachan commented on CAMEL-810:
--------------------------------------
Yeah - I kinda figured, the default for all interfaces & methods by default is
InOut. You might wanna mark some methods as InOnly and some interfaces/classes
as being all InOnly - but if you mark a class as InOnly you might wanna mark
one or two methods as being InOut.
Maybe the OneWay class name is bad; but I wanted the annotation to naturally
default to InOnly unless you explicitly specified an ExchangePattern
configuration. i.e. so just using the annotation kinda implies InOnly.
Maybe we should just use an annotation thats something like @MEP or @Pattern
with just folks knowing that by default it uses InOnly - but then I wanted the
common 80% case - adding just an annotation to mark oneway method invocations.
I think its gonna be pretty rare for folks to mark a class as @OneWay then
explicitly configure the MEP of a specific method as being not InOnly.
But maybe we need more annotations?
e.g. @InOnly, @InOut and @Pattern (for others that are not the common
InOnly/InOut)?
> 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.
