camel-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Willem Jiang <willem.ji...@gmail.com>
Subject Re: [jira] Updated: (CAMEL-1171) add from(....).inOnly("....") or from("...").inOut("....") to allow explicit ExchangePatterns to be specified in the routing DSL
Date Wed, 10 Dec 2008 12:29:54 GMT
Yes, InOnly and InOut is enough for us now.
BTW, if you want to set the ExchangePattern other than the upper 2
pattern, you could call the setExchangePattern(ExchangePattern ep) in
the builder.

Willem

Claus Ibsen wrote:
> Hi Willem
> 
> Yeah align with the SMX team what patterns is used there.
> 
> Keep the fluent builders to only commonly used
> - InOnly
> - InOut
> is fine, if that is what the SMX team always uses.
> 
> Adding all the others might confuse people what the heck a RobustInOnly is etc.
> 
> /Claus Ibsen
> Apache Camel Committer
> Blog: http://davsclaus.blogspot.com/
> 
> 
> 
> On Wed, Dec 10, 2008 at 10:45 AM, Ramon Buckland <ramon@thebuckland.com> wrote:
>> The inOnly and inOut, robustInOnly and inOptionalOut are standard MEP's so
>> would make sense to stick with them.
>> my 2cents
>>
>> On Wed, Dec 10, 2008 at 20:42, Willem Jiang (JIRA) <jira@apache.org> wrote:
>>
>>>     [
>>> https://issues.apache.org/activemq/browse/CAMEL-1171?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel]
>>>
>>> Willem Jiang updated CAMEL-1171:
>>> --------------------------------
>>>
>>>    Fix Version/s: 1.5.1
>>>
>>>> add from(....).inOnly("....") or from("...").inOut("....") to allow
>>> explicit ExchangePatterns to be specified in the routing DSL
>>> --------------------------------------------------------------------------------------------------------------------------------
>>>>                 Key: CAMEL-1171
>>>>                 URL:
>>> https://issues.apache.org/activemq/browse/CAMEL-1171
>>>>             Project: Apache Camel
>>>>          Issue Type: Improvement
>>>>            Reporter: James Strachan
>>>>            Assignee: Willem Jiang
>>>>             Fix For: 1.5.1, 2.0.0
>>>>
>>>>
>>>> Right now the *to* will use the current default pattern that an endpoint
>>> prefers. It would be good to allow it to be explicitly specified in the
>>> route.
>>>> Not 100% sure the best names to use - is *inOnly()* and *inOut()* the
>>> best? Maybe *oneway()* and *request()*?
>>>
>>> --
>>> This message is automatically generated by JIRA.
>>> -
>>> You can reply to this email to add a comment to the issue online.
>>>
>>>
> 


Mime
View raw message