[
https://issues.apache.org/jira/browse/AXIS2-1889?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_12462507
]
James Shiell commented on AXIS2-1889:
-------------------------------------
I've attached a J2SE 1.4 file.
To regenerate the issue, use a pre-defined WSDL file that references another
local file - i.e. it imports a file with a relative path (import="bob.xsd")
rather than via a URL (import="http://bob/xsd/bob.xsd";).
I have attached the OSS/J Inventory WSDL (InventoryWS.wsdl) and imported XSDs
as wsdl.zip. These are what triggered it in my case.
Thanks for you efforts - much obliged.
> WSDL with relative imports fails with FileNotFoundException.
> ------------------------------------------------------------
>
> Key: AXIS2-1889
> URL: https://issues.apache.org/jira/browse/AXIS2-1889
> Project: Apache Axis 2.0 (Axis2)
> Issue Type: Bug
> Components: wsdl
> Affects Versions: 1.1
> Environment: WLS 9.2, J2SE 1.5.0.4, Windows XP SP2
> Reporter: James Shiell
> Attachments: sample-j2se14.java, sample.java, wsdl.zip
>
>
> When using a pre-defined WSDL with relative imports the imports are not
> resolved. This appears to be because WSDLReader is always passed an empty
> base URI in WSDL11ToAxisServiceBuilder.readInTheWSDLFile(..).
> e.g.
> META-INF/service.wsdl
> META-INF/service.xsd
> If the import references "service.xsd" then the file is not found.
> I would expect it to be picked up from the same location. I would presume
> this could be accomplished by setting the base URI of the
> WSDLToAxisServiceBuilder in the DeploymentEngine.popualteService(..) method.
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators:
https://issues.apache.org/jira/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
