You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@servicemix.apache.org by "Gert Vanthienen (JIRA)" <ji...@apache.org> on 2011/02/07 03:55:30 UTC

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

    [ https://issues.apache.org/jira/browse/SMXCOMP-794?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12991255#comment-12991255 ] 

Gert Vanthienen commented on SMXCOMP-794:
-----------------------------------------

Never mind my previous comment -- that post just specifies elements in another order than the one used in the schema.  

However, now that I'm reading this issue again, this might very well be something similar.  I don't think the xbean-generated schema actually has a {{<quartz:property/>}} element - I suspect this was just syntax sugaring provided by XBean which is now failing because the Spring XSD validation happens before that.

> XBean-generated schema for components not allowing same-namespace elements (in quartz, cxfbc, cxfse, ...)
> ---------------------------------------------------------------------------------------------------------
>
>                 Key: SMXCOMP-794
>                 URL: https://issues.apache.org/jira/browse/SMXCOMP-794
>             Project: ServiceMix Components
>          Issue Type: Bug
>          Components: servicemix-cxf-bc, servicemix-cxf-se, servicemix-quartz
>    Affects Versions: servicemix-quartz-2010.01, 2011.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 (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.
-
For more information on JIRA, see: http://www.atlassian.com/software/jira