Quartz schema not allowing same-namespace elements
--------------------------------------------------
Key: SMXCOMP-794
URL: https://issues.apache.org/activemq/browse/SMXCOMP-794
Project: ServiceMix Components
Issue Type: Bug
Components: servicemix-quartz
Affects Versions: servicemix-quartz-2010.01
Reporter: Zac Wolfe
A problem with the schema contained in the servicemix-quartz component jar is
preventing valid quartz endpoint xml configuration code from working. Code
that was valid in previous versions, such as the following taken from the
servicemix online documentation
(http://servicemix.apache.org/servicemix-quartz.html) is no longer working:
<quartz:endpoint service="test:service" endpoint="endpoint3"
targetService="test:receiver3">
<quartz:jobDetail>
<quartz:jobDetail>
<quartz:jobDataAsMap>
<quartz:property key="xml"><![CDATA[
<hello>world</hello>
]]></quartz:property>
</quartz:jobDataAsMap>
</quartz:jobDetail>
</quartz:jobDetail>
<quartz:triggers>
<quartz:simple repeatCount="0" repeatInterval="1000" />
<quartz:cron cronExpression="0 * 1 * * ?" />
</quartz:triggers>
<quartz:marshaler>
<bean class="org.apache.servicemix.quartz.CustomMarshaler" />
</quartz:marshaler>
</quartz:endpoint>
This is caused by the fact that the .xsd doesn't allow child elements to belong
to a different namespace:
<xs:element name='jobDataAsMap' minOccurs='0' maxOccurs='1'>
<xs:complexType>
<xs:sequence minOccurs='0' maxOccurs='unbounded'><xs:any
namespace='##other'/></xs:sequence>
</xs:complexType>
</xs:element>
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
