[
https://issues.apache.org/activemq/browse/CAMEL-195?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=42095#action_42095
]
Jonathan Anstey commented on CAMEL-195:
---------------------------------------
Hmmm... yeah, I believe this is a side effect of me extending from the
ExpressionNode in the SetHeaderType JAXB object. From the schema, it appears
though that the child processor is optional, so you should be able to safely
omit it. Also, the underlying SetHeaderProcessor does not require it. See the
following snippet from
http://activemq.apache.org/camel/schema/spring/camel-spring.xsd
{code}
<xs:complexType name="expressionNode">
<xs:complexContent>
<xs:extension base="tns:processorType">
<xs:sequence>
<xs:element ref="tns:interceptor" maxOccurs="unbounded"
minOccurs="0"/>
<xs:choice maxOccurs="1" minOccurs="1">
<xs:element ref="tns:el"/>
...
<xs:element ref="tns:xpath"/>
<xs:element ref="tns:xquery"/>
</xs:choice>
<xs:choice maxOccurs="unbounded" minOccurs="0">
<xs:element ref="tns:aggregator"/>
...
<xs:element ref="tns:to"/>
<xs:element ref="tns:try"/>
</xs:choice>
</xs:sequence>
</xs:extension>
</xs:complexContent>
</xs:complexType>
{code}
> support convertBody() intercept() setHeader() into the XML DSL
> --------------------------------------------------------------
>
> Key: CAMEL-195
> URL: https://issues.apache.org/activemq/browse/CAMEL-195
> Project: Apache Camel
> Issue Type: Improvement
> Components: camel-core
> Reporter: James Strachan
> Assignee: Jonathan Anstey
> Fix For: 1.4.0
>
> Attachments: camel-195.patch
>
>
> See the discussion: :
> http://www.nabble.com/How-to-do-that-in-Camel-XML-%28again%29---tf4647505s22882.html#a13276113
> we need to add more of the built in Java processors to the XSD...
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
