[ http://issues.apache.org/jira/browse/MUSE-89?page=all ]

Dan Jemiolo updated MUSE-89:
----------------------------

      Component/s: Core Engine - WSDL Processing
                       (was: Tooling - Code Generation)
          Summary: WSDL import resolution does not handle remote URIs 
(http://...)  (was: Resolving imports and includes is incorrect)
    Fix Version/s: 2.2.0
                       (was: 2.1.0)
      Description: 
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.

  was:
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.

         Priority: Minor  (was: Major)

I believe your reasoning is current on the WSDL paths - not sure if you want to 
do the remote file support. I have renamed this issue, moved it to 2.2, and 
will let you decide on its priority.

> WSDL import resolution does not handle remote URIs (http://...)
> ---------------------------------------------------------------
>
>                 Key: MUSE-89
>                 URL: http://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.
-
If you think it was sent incorrectly contact one of the administrators: 
http://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]

Reply via email to