[ 
https://issues.apache.org/jira/browse/ODE-879?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12894889#action_12894889
 ] 

Markus Piff commented on ODE-879:
---------------------------------

This applies indirectly to ODE as well, although the issue needs to be solved 
within Xerces.

When an ODE process imports a wsdl file, which itself imports an "invalid" xsd 
(directly or indirectly through the dependency graph), the presented issue 
arises. 

This can easily be reproduced by including the following within the processes 
wsdl file:

<xsd:import 

                  namespace="http://schemas.xmlsoap.org/ws/2005/02/trust";

                  
schemaLocation="http://schemas.xmlsoap.org/ws/2005/02/trust/ws-trust.xsd"/>

ws-trust is "valid" and can be imported without any problems, however the 
schema itself indirectly imports 
http://www.w3.org/TR/xmldsig-core/xmldsig-core-schema.xsd, which isn't valid. 
Then at deployment time, java.lang.IllegalArgumentException: Null model. is 
thrown.

Unfortunately I didn't have time yet to investigate the problem further (which 
Xerces versions are affected, etc), therefore no issue exists so far. 

> Incorrect import/include/redefine of xml schema files
> -----------------------------------------------------
>
>                 Key: ODE-879
>                 URL: https://issues.apache.org/jira/browse/ODE-879
>             Project: ODE
>          Issue Type: Bug
>          Components: BPEL Compilation/Parsing
>    Affects Versions: 2.0-beta2
>            Reporter: Markus Piff
>   Original Estimate: 0.5h
>  Remaining Estimate: 0.5h
>
> ODE expects that xsd files must start with the xsd:schema element. However 
> this assumption is NOT valid.
> E.g. http://www.w3.org/TR/xmldsig-core/xmldsig-core-schema.xsd references a 
> DTD, thereby breaks ODE's assumption. This results in a schema error followed 
> by java.lang.IllegalArgumentException: Null model.
> The problem arises when one imports a wsdl file within the bpel process, 
> which itself imports/includes/redefines xsd files which don't comply with the 
> assumption.

-- 
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.

Reply via email to