servicemix-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Gert Vanthienen (JIRA)" <>
Subject [jira] Commented: (SMXCOMP-794) Quartz schema not allowing same-namespace elements
Date Mon, 07 Feb 2011 02:07:30 GMT


Gert Vanthienen commented on SMXCOMP-794:

As indicated by Zac, the problem lies the use of {{<xsd:any namemspace="##other">}}
in the xbean-generated xsd file, where {{##other}} means that the child elements can not be
from the same namespace as the parent tag.  This is causing XML validation to fail because
the {{<quartz:property/>}} does belong to the same namespace as the {{<quartz:jobDataAsMap}}

The schema validation errors aren't showing up in the unit tests because we disabled validation
there (cfr.
and they weren't showing up in previous releases of ServiceMix because earlier versions of
Spring were less strict in validating the XML.

> Quartz schema not allowing same-namespace elements
> --------------------------------------------------
>                 Key: SMXCOMP-794
>                 URL:
>             Project: ServiceMix Components
>          Issue Type: Bug
>          Components: servicemix-quartz
>    Affects Versions: servicemix-quartz-2010.01
>            Reporter: Zac Wolfe
>            Assignee: Jean-Baptiste Onofré
> 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 (
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.
For more information on JIRA, see:


View raw message