Arthur, I don't think the test case is invalid. I checked the WSDL2 spec. There are no assertions stating that an *inlined* schema must have a targetNamespace. Assertion Schema-1069 requires only *imported* schemas to have a targetNamespace.
The WSDL does not declare a default namespace and the inlined <xs:schema> element does not define a targetNamespace, so the ElementDeclarations have no namespace URI (i.e. their QNames have the empty string as the namespace URI) and the 'element' references in the <input> and <output> elements have no namespace prefix (this OK according to the definition of the xs:QName type in the Namespaces in XML spec [1]). Those 'element' references do now resolve correctly to the corresponding ElementDeclarations (after applying the WODEN-172 fix). [1] http://www.w3.org/TR/1999/REC-xml-names-19990114/#NT-QName John Kaputin "Arthur Ryman" <[EMAIL PROTECTED]> wrote on 01/08/2007 01:20:34: > John, > > Is the test case invalid? If so, please post the correction to W3C. Thx. > > -- Arthur > > > On 7/31/07, John Kaputin (JIRA) <[EMAIL PROTECTED]> wrote: > FlickrHTTP-1G test fails because xs:QName values without a prefix > are handled incorrectly > ----------------------------------------------------------------------------------------- > > 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] Unless stated otherwise above: IBM United Kingdom Limited - Registered in England and Wales with number 741598. Registered office: PO Box 41, North Harbour, Portsmouth, Hampshire PO6 3AU --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
