[ 
https://issues.apache.org/jira/browse/WODEN-216?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12630264#action_12630264
 ] 

W. Brian Gourlie commented on WODEN-216:
----------------------------------------

I have finally been able to reproduce this bug - while actually trying to 
reproduce a different bug, which I will submit a separate issue for.  I have 
attached a zip file with all necessary files.  The WSDL (saved as .xml) 
includes a processing instruction telling it to use the wsdl-viewer 
transformation.  I have included two versions of the WSDL viewer, revision 
r602769 and the HEAD revision.  Using the older revision, the WSDL viewer can 
resolve all relative imports, however will fall into an infinite loop due to a 
circular reference within the XSD's (which is the other issue).  The HEAD 
revision will fail to transform (using Microsofts XSLT processor, Mozilla's 
will simply ignore it and not show any source for the XSD) because it is unable 
to resolve a relative import.

To reproduce, simply open the SomeService_WSDL_.xml in IE.  Change the 
processing instruction to specify the old or new wsdl-viewer to see the 
difference.  Again, using the old revision of WSDL-Viewer, this will cause an 
infinite loop.  I assume the new revision would suffer the same issue if it 
were to resolve all imports.  

> WSDL-Viewer no longer able to resolve relative url for XSD's in certain 
> situations
> ----------------------------------------------------------------------------------
>
>                 Key: WODEN-216
>                 URL: https://issues.apache.org/jira/browse/WODEN-216
>             Project: Woden
>          Issue Type: Bug
>          Components: Tools
>    Affects Versions: M9
>         Environment: MS/Mozilla XSLT Processors
>            Reporter: W. Brian Gourlie
>            Assignee: Tomi Vanek
>         Attachments: wsdl-viewer-bug-reproduced.zip
>
>
> Wsdl-viewer is not able to resolve XSD's that have relative URL's (in certain 
> cases that I was not able to reproduce on my machine locally).  It appears 
> that some "magic" was removed from the latest committed patch (r61170), since 
> the previous version was able to do so, and still does when used in place of 
> the newest revision.  

-- 
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]

Reply via email to