[
https://issues.apache.org/jira/browse/CAMEL-3708?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Claus Ibsen resolved CAMEL-3708.
--------------------------------
Resolution: Fixed
trunk: 1073776.
> Tidy up AST model to proper support output or not
> -------------------------------------------------
>
> Key: CAMEL-3708
> URL: https://issues.apache.org/jira/browse/CAMEL-3708
> Project: Camel
> Issue Type: Improvement
> Components: camel-core, camel-spring
> Affects Versions: 2.6.0
> Reporter: Claus Ibsen
> Assignee: Claus Ibsen
> Fix For: 2.7.0
>
>
> We should tidy up the model, so they clearly indicate if
> - outputs supported
> - no outputs
> eg when an EIP supports output, they can be nested/added to it, eg in XML its
> like
> {code:xml}
> <split>
> <output 1>
> <output 2>
> </split>
> {code}
> But some EIPs indicate they support output, but they dont. For example <to>
> should not support output as it doesn't make sense.
> We should introduce a {{isOutputSupported}} on the {{ProcessorDefinition}}
> and then check each EIP.
> This will cause changes to the XSD in that regard EIPs which really didn't
> support output (eg it was hacked that way in Java code) but the XSD would
> allow outputs, eg
> {code:xml}
> <to uri="xxx">
> <output 1>
> <output 2>
> </to>
> {code}
> Now this would not be possible and you would have to do
> {code:xml}
> <to uri="xxx"/>
> <output 1>
> <output 2>
> {code}
> This will in fact reduce the XSD and make it more concise when outputs is
> supported or not.
--
This message is automatically generated by JIRA.
-
For more information on JIRA, see: http://www.atlassian.com/software/jira
