[
https://issues.apache.org/activemq/browse/SM-980?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_39940
]
Jevgeni Holodkov commented on SM-980:
-------------------------------------
By the way, I have found out, that this doesn't work only if import statement
is under <wsdl:types> tag. If it directly under <wsdl:definitions> tag, then it
works perfectly.
> Relative schema import in WSDL is failed with EIP component
> -----------------------------------------------------------
>
> Key: SM-980
> URL: https://issues.apache.org/activemq/browse/SM-980
> Project: ServiceMix
> Issue Type: Bug
> Components: servicemix-eip
> Affects Versions: 3.2
> Environment: Tomcat 5.5, Windows 2000
> Reporter: Jevgeni Holodkov
> Attachments: EIP-relative-schema-import.txt, local-1.xml.zip
>
>
> A WSDL file contains <xsd:import> with schemaLocation set to relative
> resource:
> <xs:import namespace="http://mynamespace.com";
> schemaLocation="DomainOperation.xsd"/>
> If I attach it to EIP component as wsdlResource and try to access it through
> the HTTP component, then the following exception is thrown:
> {quote}
> WARN - WSDL1Processor - Error retrieving interfaces from service
> description: WSDLException (at /wsdl:definitions/wsdl:types/xs:schema):
> faultCode=OTHER_ERROR: An error occurred trying to resolve schema referenced
> at 'DomainOperation.xsd'.: java.io.FileNotFoundException: This file was not
> found: file:/C:/dev/tomcat_55/bin/DomainOperation.xsd
> {quote}
> This issue is similar to JSR181 component
> ([SM-727|http://issues.apache.org/activemq/browse/SM-727]), but now it is
> related to EIP component. I attach my patch and the mylyn context. In my
> patch I've supposed, that other components can also be prone to error in this
> case, so I pushed down updateDefinitions() method to Endpoint class.
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
