You are viewing a plain text version of this content. The canonical link for it is here.
Posted to muse-dev@ws.apache.org by "Steve Jerman (JIRA)" <ji...@apache.org> on 2006/09/03 17:12:22 UTC
[jira] Created: (MUSE-89) Resolving imports and includes is
incorrect
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
[jira] Updated: (MUSE-89) WSDL import resolution does not handle
remote URIs (http://...)
Posted by "Dan Jemiolo (JIRA)" <ji...@apache.org>.
[ 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: muse-dev-unsubscribe@ws.apache.org
For additional commands, e-mail: muse-dev-help@ws.apache.org
[jira] Resolved: (MUSE-89) WSDL import resolution does not handle
remote URIs (http://...)
Posted by "Andrew Eberbach (JIRA)" <ji...@apache.org>.
[ 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: muse-dev-unsubscribe@ws.apache.org
For additional commands, e-mail: muse-dev-help@ws.apache.org
[jira] Assigned: (MUSE-89) Resolving imports and includes is
incorrect
Posted by "Andrew Eberbach (JIRA)" <ji...@apache.org>.
[ http://issues.apache.org/jira/browse/MUSE-89?page=all ]
Andrew Eberbach reassigned MUSE-89:
-----------------------------------
Assignee: Andrew Eberbach (was: Dan Jemiolo)
> 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
> Affects Versions: 2.0.0 M2
> Reporter: Steve Jerman
> Assigned To: Andrew Eberbach
> Fix For: 2.1.0
>
>
> 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
[jira] Updated: (MUSE-89) Resolving imports and includes is
incorrect
Posted by "Dan Jemiolo (JIRA)" <ji...@apache.org>.
[ http://issues.apache.org/jira/browse/MUSE-89?page=all ]
Dan Jemiolo updated MUSE-89:
----------------------------
Fix Version/s: 2.1.0
Affects Version/s: 2.0.0 M2
> 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
> Affects Versions: 2.0.0 M2
> Reporter: Steve Jerman
> Assigned To: Dan Jemiolo
> Fix For: 2.1.0
>
>
> 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
[jira] Commented: (MUSE-89) Resolving imports and includes is
incorrect
Posted by "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