[jira] Commented: (MUSE-89) Resolving imports and includes is incorrect

["Andrew Eberbach (JIRA)" <ji...@apache.org>]

    [ http://issues.apache.org/jira/browse/MUSE-89?page=comments#action_12432365 ] 
            
Andrew Eberbach commented on MUSE-89:
-------------------------------------

Hi,

The http URL is a known limitation, however I think the locations being relative to the directory is the way the specs usually define it. For example:

http://www.w3.org/TR/1999/REC-html401-19991224/intro/intro.html#h-2.1.3

The WSDL spec doesn't really say anything about relative paths besides saying that they are allowed. I think wsdl4j also follows this convention but I'll double check this. We definitely don't want to limit people to putting all of their WSDLs into one directory, since in the eclipse tooling we're doing we definitely reference relative-path WSDL documents. Can you give me an example of where this is failing and what the directory structure looks like? 

The thing that I'm still unsure about is the semantics of a relative path in the following situation. Say you have a document foo.wsdl and it references another document, bar.wsdl, with:

location="bar.wsdl"

How does this get resolved relative to the file? If we were to take the location of the file, say:

/usr/www/wsdls/foo.wsdl

and append bar.wsdl

/usr/www/wsdls/foo.wsdl/bar.wsdl

that seems to imply that bar.wsdl is a child of foo.wsdl, yet foo.wsdl is a file, not a directory. From my understanding the canonical interpretation is supposed to be that bar.wsdl is a sibling. 

The relative path that starts with .. is what makes this case ambiguous. If the location for the include was:

location="../bar.wsdl"

this would technically make sense because you would have:

/usr/www/wsdls/foo.wsdl/../bar.wsdl

Which would resolve to

/usr/www/wsdls/bar.wsdl

However, that turns the case of including a WSDL file without any path information into always having to have .. prepended to the path of WSDLs that are in the same directory. If I've misinterpreted the specs please let me know, this is an issue that we raised internally during development but went through (basically) the above reasoning and then closed on the issue.

Thanks,
Andrew

Thanks,
Andrew

> Resolving imports and includes is incorrect
> -------------------------------------------
>
>                 Key: MUSE-89
>                 URL: http://issues.apache.org/jira/browse/MUSE-89
>             Project: Muse
>          Issue Type: Bug
>          Components: Tooling - Code Generation
>            Reporter: Steve Jerman
>         Assigned To: Dan Jemiolo
>
> 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: muse-dev-unsubscribe@ws.apache.org
For additional commands, e-mail: muse-dev-help@ws.apache.org