[
https://issues.apache.org/jira/browse/WODEN-172?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
John Kaputin updated WODEN-172:
-------------------------------
Summary: FlickrHTTP-1G test fails due to NS prefix and interface extension
errors (was: FlickrHTTP-1G test fails because xs:QName values without a prefix
are handled incorrectly)
Once the namespace prefix error was resolved it highlighted a new problem. The
Flickr WSDL uses several (i.e. more than 2) levels of interface extension. When
Woden retrieves all operations for an interface (i.e. directly declared and
derived operations) is only searches the interfaces extended directly by the
current interface, but not any interfaces that those interfaces extend.
The fix is to change the behaviour of Woden to search the entire interface
extension tree so that the operations (and faults) available to an interface
will include:
1. the operations declared directly by the interface
2. the operations declared by any interfaces that this interface extends,
directly or indirectly
> FlickrHTTP-1G test fails due to NS prefix and interface extension errors
> ------------------------------------------------------------------------
>
> Key: WODEN-172
> URL: https://issues.apache.org/jira/browse/WODEN-172
> Project: Woden
> Issue Type: Bug
> Reporter: John Kaputin
> Assignee: John Kaputin
> Fix For: M8
>
>
> The FlickrHTTP-1G testcase fails with messages like:
> Woden[Error],0:0,WSDL505,Could not create a QName from the string
> "activity.userComments" in element "{http://www.w3.org/ns/wsdl}input";.
> for each occurrence of a xs:QName attribute value that does not contain a
> namespace prefix. Adding a default namespace declaration to the WSDL that is
> equivalent to the target NS will eliminate these errors, but this is not
> solving the fundamental problem. This problem is that when Woden attempts to
> create a QName object from such a prefix-less xs:QName value, it should
> simply pass a null value as the namespaceURI argument to the QName ctor.
> Instead it assumes there has been some error resolving a namespace prefix to
> a namespace URI and throws a WSDLException.
> The solution is to check if a prefix was present in the xs:QName value before
> attempting prefix resolution and if not, then just pass null to the ctor as
> above.
--
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]
