Bug #62891 for XML-Compile-SOAP: cannot parse sawdsl attrExtension tags

Wed Nov 10 06:09:12 2010 http://www.google.com/profiles/109749655677560058134 - Ticket created

Subject:

cannot parse sawdsl attrExtension tags

perl v5.10.0 built for darwin-thread-multi-2level Mac OS 10.6.4 'Snow Leopard' XML-Compile-SOAP-2.18 XML::Compile throws an error when parsing the wsdl: error: element `{http://schemas.xmlsoap.org/wsdl/}portType' not processed at {http://schemas.xmlsoap.org/wsdl/}definitions The portType definition has one element which seems to be causing this: <sawsdl:attrExtensions sawsdl:modelReference="http://purl.obolibrary.org/obo/EDAM_0000493"/> Works if the sawsdl attrExtension tags are removed. WSDL is WSI compliant.

Wed Nov 10 08:37:13 2010 solutions [...] overmeer.net - Correspondence added

Subject:	Re: [rt.cpan.org #62891] cannot parse sawdsl attrExtension tags
Date:	Wed, 10 Nov 2010 14:36:58 +0100
To:	"http://www.google.com/profiles/109749655677560058134 via RT" <bug-XML-Compile-SOAP [...] rt.cpan.org>
From:	Mark Overmeer <solutions [...] overmeer.net>

* http://www.google.com/profiles/109749655677560058134 via RT (bug-XML-Compile-SOAP@rt.cpan.org) [101110 12:09]: Show quoted text

> Wed Nov 10 06:09:12 2010: Request 62891 was acted upon. > Queue: XML-Compile-SOAP > Subject: cannot parse sawdsl attrExtension tags > Ticket <URL: https://rt.cpan.org/Ticket/Display.html?id=62891 > > > XML::Compile throws an error when parsing the wsdl: > error: element `{http://schemas.xmlsoap.org/wsdl/}portType' not processed at > {http://schemas.xmlsoap.org/wsdl/}definitions > > The portType definition has one element which seems to be causing this: > <sawsdl:attrExtensions > sawsdl:modelReference="http://purl.obolibrary.org/obo/EDAM_0000493"/> > Works if the sawsdl attrExtension tags are removed.

The portType declaration, you mean. The portType definition is: <xs:complexType name="tPortType"> <xs:complexContent> <xs:extension base="wsdl:tExtensibleAttributesDocumented"> <xs:sequence> <xs:element name="operation" type="wsdl:tOperation" minOccurs="0" maxOccurs="unbounded"/> </xs:sequence> <xs:attribute name="name" type="xs:NCName" use="required"/> </xs:extension> </xs:complexContent> </xs:complexType> <xs:complexContent> <xs:extension base="wsdl:tDocumented"> <xs:annotation> <xs:documentation> This type is extended by component types to allow attributes from other namespaces to be added. </xs:documentation> </xs:annotation> <xs:anyAttribute namespace="##other" processContents="lax"/> </xs:extension> </xs:complexContent> </xs:complexType> <xs:complexType name="tDocumented"> <xs:annotation> <xs:documentation> This type is extended by component types to allow them to be documented </xs:documentation> </xs:annotation> <xs:sequence> <xs:element name="documentation" type="wsdl:tDocumentation" minOccurs="0"/> </xs:sequence> </xs:complexType> As the name of the base-class says: it only permits anyAttributes, not "any" elements. So the SAWSDL extension does not obey the WSDL11 standard. Which is not conflicting with its webpage on http://www.w3.org/2002/ws/sawsdl ... developing a mechanism to enable semantic annotation of Web services descriptions in WSDL 2.0. Show quoted text

> WSDL is WSI compliant.

That doesn't say a thing: everyone made-up their own extension standards... On the other hand... hacks are not uncommon: there are many XML extensions which do not respect the rules... that is no reason to deny you request to get some kind of support for it. It would be implemented like XML::Compile::SOAP::WSA, probably best called XML::Compile::SAWSDL::WSDL11 and ::SAWSDL::Schema. Please your ideas. It will probably take me a few hours to get a clean implementation out. Is it often used? -- Regards, MarkOv ------------------------------------------------------------------------ Mark Overmeer MSc MARKOV Solutions Mark@Overmeer.net solutions@overmeer.net http://Mark.Overmeer.net http://solutions.overmeer.net

Wed Nov 10 08:37:14 2010 The RT System itself - Status changed from 'new' to 'open'

Fri Nov 12 07:08:28 2010 http://www.google.com/profiles/109749655677560058134 - Correspondence added

From:

francisco [...] roque.com.pt

Thank you very much for your attention to this issue. I'll send you a more detailed description of the problem and possible solutions after I go through all the related standards. Regards On Wed Nov 10 08:37:13 2010, solutions@overmeer.net wrote: Show quoted text

> * http://www.google.com/profiles/109749655677560058134 via RT (bug- > XML-Compile-SOAP@rt.cpan.org) [101110 12:09]:

> > Wed Nov 10 06:09:12 2010: Request 62891 was acted upon. > > Queue: XML-Compile-SOAP > > Subject: cannot parse sawdsl attrExtension tags > > Ticket <URL: https://rt.cpan.org/Ticket/Display.html?id=62891 > > > > > XML::Compile throws an error when parsing the wsdl: > > error: element `{http://schemas.xmlsoap.org/wsdl/}portType' not

> processed at

> > {http://schemas.xmlsoap.org/wsdl/}definitions > > > > The portType definition has one element which seems to be causing

> this:

> > <sawsdl:attrExtensions > >

> sawsdl:modelReference="http://purl.obolibrary.org/obo/EDAM_0000493"/>

> > Works if the sawsdl attrExtension tags are removed.

> > The portType declaration, you mean. The portType definition is: > > <xs:complexType name="tPortType"> > <xs:complexContent> > <xs:extension base="wsdl:tExtensibleAttributesDocumented"> > <xs:sequence> > <xs:element name="operation" type="wsdl:tOperation" > minOccurs="0" maxOccurs="unbounded"/> > </xs:sequence> > <xs:attribute name="name" type="xs:NCName" use="required"/> > </xs:extension> > </xs:complexContent> > </xs:complexType> > > <xs:complexContent> > <xs:extension base="wsdl:tDocumented"> > <xs:annotation> > <xs:documentation> > This type is extended by component types to allow attributes > from other namespaces to be added. > </xs:documentation> > </xs:annotation> > <xs:anyAttribute namespace="##other" processContents="lax"/> > </xs:extension> > </xs:complexContent> > </xs:complexType> > > <xs:complexType name="tDocumented"> > <xs:annotation> > <xs:documentation> > This type is extended by component types to allow them to be > documented > </xs:documentation> > </xs:annotation> > <xs:sequence> > <xs:element name="documentation" type="wsdl:tDocumentation" > minOccurs="0"/> > </xs:sequence> > </xs:complexType> > > As the name of the base-class says: it only permits anyAttributes, not > "any" > elements. So the SAWSDL extension does not obey the WSDL11 standard. > Which > is not conflicting with its webpage on > http://www.w3.org/2002/ws/sawsdl > > ... developing a mechanism to enable semantic annotation of Web > services > descriptions in WSDL 2.0. >

> > WSDL is WSI compliant.

> > That doesn't say a thing: everyone made-up their own extension > standards... > > On the other hand... hacks are not uncommon: there are many XML > extensions > which do not respect the rules... that is no reason to deny you > request > to get some kind of support for it. It would be implemented like > XML::Compile::SOAP::WSA, probably best called > XML::Compile::SAWSDL::WSDL11 > and ::SAWSDL::Schema. > > Please your ideas. It will probably take me a few hours to get a clean > implementation out. Is it often used?

Mon Nov 15 10:24:04 2010 http://www.google.com/profiles/109749655677560058134 - Correspondence added

From:

francisco [...] roque.com.pt

Hi, I found out what was happening. When I changed the order of the attrExtensions tag towards right after the documentation tag, I no longer get an error. Check below: <operation name="GetData"> <documentation> Retrieves the resulting data of the short read alignments </documentation> <sawsdl:attrExtensions sawsdl:modelReference="http://purl.obolibrary.org/obo/EDAM_0000493"/> <input message="tns:GetDataRequestMsg"> </input> <output message="tns:GetDataResponseMsg"> </output> <fault name="fault" message="tns:GetData_faultMsg"> </fault> </operation> This might be due just to a very strict wsdl parsing, but as long as I comply with it there should be no problem. Thanks. On Fri Nov 12 07:08:28 2010, http://www.google.com/profiles/109749655677560058134 wrote: Show quoted text

> Thank you very much for your attention to this issue. > > I'll send you a more detailed description of the problem and possible > solutions after I go > through all the related standards. > > Regards > > > > On Wed Nov 10 08:37:13 2010, solutions@overmeer.net wrote:

> > * http://www.google.com/profiles/109749655677560058134 via RT (bug- > > XML-Compile-SOAP@rt.cpan.org) [101110 12:09]:

> > > Wed Nov 10 06:09:12 2010: Request 62891 was acted upon. > > > Queue: XML-Compile-SOAP > > > Subject: cannot parse sawdsl attrExtension tags > > > Ticket <URL: https://rt.cpan.org/Ticket/Display.html?id=62891 > > > > > > > XML::Compile throws an error when parsing the wsdl: > > > error: element `{http://schemas.xmlsoap.org/wsdl/}portType' not

> > processed at

> > > {http://schemas.xmlsoap.org/wsdl/}definitions > > > > > > The portType definition has one element which seems to be causing

> > this:

> > > <sawsdl:attrExtensions > > >

> >

> sawsdl:modelReference="http://purl.obolibrary.org/obo/EDAM_0000493"/>

> > > Works if the sawsdl attrExtension tags are removed.

> > > > The portType declaration, you mean. The portType definition is: > > > > <xs:complexType name="tPortType"> > > <xs:complexContent> > > <xs:extension base="wsdl:tExtensibleAttributesDocumented"> > > <xs:sequence> > > <xs:element name="operation" type="wsdl:tOperation" > > minOccurs="0" maxOccurs="unbounded"/> > > </xs:sequence> > > <xs:attribute name="name" type="xs:NCName" use="required"/> > > </xs:extension> > > </xs:complexContent> > > </xs:complexType> > > > > <xs:complexContent> > > <xs:extension base="wsdl:tDocumented"> > > <xs:annotation> > > <xs:documentation> > > This type is extended by component types to allow

> attributes

> > from other namespaces to be added. > > </xs:documentation> > > </xs:annotation> > > <xs:anyAttribute namespace="##other" processContents="lax"/> > > </xs:extension> > > </xs:complexContent> > > </xs:complexType> > > > > <xs:complexType name="tDocumented"> > > <xs:annotation> > > <xs:documentation> > > This type is extended by component types to allow them to be > > documented > > </xs:documentation> > > </xs:annotation> > > <xs:sequence> > > <xs:element name="documentation" type="wsdl:tDocumentation" > > minOccurs="0"/> > > </xs:sequence> > > </xs:complexType> > > > > As the name of the base-class says: it only permits anyAttributes,

> not

> > "any" > > elements. So the SAWSDL extension does not obey the WSDL11 standard. > > Which > > is not conflicting with its webpage on > > http://www.w3.org/2002/ws/sawsdl > > > > ... developing a mechanism to enable semantic annotation of Web > > services > > descriptions in WSDL 2.0. > >

> > > WSDL is WSI compliant.

> > > > That doesn't say a thing: everyone made-up their own extension > > standards... > > > > On the other hand... hacks are not uncommon: there are many XML > > extensions > > which do not respect the rules... that is no reason to deny you > > request > > to get some kind of support for it. It would be implemented like > > XML::Compile::SOAP::WSA, probably best called > > XML::Compile::SAWSDL::WSDL11 > > and ::SAWSDL::Schema. > > > > Please your ideas. It will probably take me a few hours to get a

> clean

> > implementation out. Is it often used?

> >

Mon Nov 15 10:31:13 2010 Mark [...] Overmeer.net - Correspondence added

Subject:	Re: [rt.cpan.org #62891] cannot parse sawdsl attrExtension tags
Date:	Mon, 15 Nov 2010 16:30:56 +0100
To:	"http://www.google.com/profiles/109749655677560058134 via RT" <bug-XML-Compile-SOAP [...] rt.cpan.org>
From:	Mark Overmeer <mark [...] overmeer.net>

* http://www.google.com/profiles/109749655677560058134 via RT (bug-XML-Compile-SOAP@rt.cpan.org) [101115 16:24]: Show quoted text

> Queue: XML-Compile-SOAP > Ticket <URL: https://rt.cpan.org/Ticket/Display.html?id=62891 > > > I found out what was happening. When I changed the order of the > attrExtensions tag towards right after the documentation tag, I no > longer get an error. Check below:

On tht spot, "any" elements are accepted by the WSDL schema. Show quoted text

> This might be due just to a very strict wsdl parsing, but as long > as I comply with it there should be no problem.

What is the use of schema's if you do not follow them? What to do? Close the ticket? Implement the extension? -- Regards, MarkOv ------------------------------------------------------------------------ Mark Overmeer MSc MARKOV Solutions Mark@Overmeer.net solutions@overmeer.net http://Mark.Overmeer.net http://solutions.overmeer.net

Mon Nov 15 10:32:08 2010 http://www.google.com/profiles/109749655677560058134 - Correspondence added

Please close the ticket. On Mon Nov 15 10:31:13 2010, Mark@Overmeer.net wrote: Show quoted text

> * http://www.google.com/profiles/109749655677560058134 via RT (bug- > XML-Compile-SOAP@rt.cpan.org) [101115 16:24]:

> > Queue: XML-Compile-SOAP > > Ticket <URL: https://rt.cpan.org/Ticket/Display.html?id=62891 > > > > > I found out what was happening. When I changed the order of the > > attrExtensions tag towards right after the documentation tag, I no > > longer get an error. Check below:

> > On tht spot, "any" elements are accepted by the WSDL schema. >

> > This might be due just to a very strict wsdl parsing, but as long > > as I comply with it there should be no problem.

> > What is the use of schema's if you do not follow them? > > What to do? Close the ticket? Implement the extension?

Tue Nov 16 03:18:56 2010 MARKOV [...] cpan.org - Correspondence added

not a bug

Tue Nov 16 03:18:56 2010 MARKOV [...] cpan.org - Status changed from 'open' to 'resolved'