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 <[EMAIL PROTECTED]> 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) <[EMAIL PROTECTED]> 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. >> >> >
