[SMXCOMP-794] XBean-generated schema for components not allowing same-namespace elements (in quartz, cxfbc, cxfse, ...)

• Type: Bug
• Status: Open
• Priority: Major
• Resolution: Unresolved
• Affects Version/s: servicemix-quartz-2010.01, 2011.01
• Fix Version/s: 2013.02
• Component/s: servicemix-cxf-bc, servicemix-cxf-se, servicemix-quartz
• Regression: Regression
• Assignee: Jean-Baptiste Onofré
• Reporter: Zac Wolfe
• Created: 31/Aug/10 16:37
• Updated: 10/Dec/12 10:12

Description

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>