[
https://issues.apache.org/jira/browse/MUSE-89?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Andrew Eberbach resolved MUSE-89.
---------------------------------
Resolution: Fixed
Added a WsdlEnvironment that handles this case. This also needed a change to
the AbstractEnvironment to create the correct relative paths.
> WSDL import resolution does not handle remote URIs (http://...)
> ---------------------------------------------------------------
>
> Key: MUSE-89
> URL: https://issues.apache.org/jira/browse/MUSE-89
> Project: Muse
> Issue Type: Bug
> Components: Core Engine - WSDL Processing
> Affects Versions: 2.0.0 M2
> Reporter: Steve Jerman
> Assigned To: Andrew Eberbach
> Priority: Minor
> Fix For: 2.2.0
>
>
> Imported and included schemas or namespaces can have a location that is
> remote. We should be able to use java.net.URL & URLConnection to get the
> content of these remote files, build a DOM, and continue building the WSDL as
> normal. This will make it easier for people who have OASIS/W3C/etc. WSDLs
> that refer to files remotely, since they don't have to go find all of the
> files from /docs.
> ORIGINAL DESCRIPTION
> ------------------------------------
> All imported and included namespace locations are relative to the directory
> that contains the starting wsdl file... this is incorrect.
> * They should be relative to the file doing the include/import
> * The locations can be http URLS.. these don't work so you have to modify the
> 'standard' XSDs
> The implementation basically mean that you are restricted to using a single
> directory for you XSD and fix all locations to be just the file names.
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
