Skip Menu |

This queue is for tickets about the XML-Compile-WSDL11 CPAN distribution.

Report information
The Basics
Id: 105270
Status: rejected
Priority: 0/
Queue: XML-Compile-WSDL11

People
Owner: Nobody in particular
Requestors: mitchell.ianj [...] yahoo.com
Cc:
AdminCc:

Bug Information
Severity: (no value)
Broken in: (no value)
Fixed in: (no value)



Subject: Bug report for WSDL11.pm
Date: Tue, 16 Jun 2015 15:54:04 +0000 (UTC)
To: "bug-XML-Compile-WSDL11 [...] rt.cpan.org" <bug-XML-Compile-WSDL11 [...] rt.cpan.org>
From: Ian Mitchell <mitchell.ianj [...] yahoo.com>
On line 169 of WSDL11.pm, the code contains: {  my $addr_label = first { /_address$/ } keys %$port The line should contain: {  my $addr_label = first { /address$/ } keys %$port Rational from my perspective: WSDL port definitions typically contains "<soap:address...." and the regular expression used to match the address is expecting a "_" character, this is causing legitimate address definitions in wsdl:ports to be ignored. Perhaps this is a change in how regular expressions are processed in later versions of Perl from what I'm running (5.10)? Thank you,Ian Mitchell
On Tue Jun 16 11:54:13 2015, mitchell.ianj@yahoo.com wrote: Show quoted text
> > On line 169 of WSDL11.pm, the code contains: > {  my $addr_label = first { /_address$/ } keys %$port > The line should contain: > {  my $addr_label = first { /address$/ } keys %$port > Rational from my perspective: > WSDL port definitions typically contains "<soap:address...." and the > regular expression used to match the address is expecting a "_" > character, this is causing legitimate address definitions in > wsdl:ports to be ignored.
You are wrong. XML::Compile supports rewrite rules on names (of elements and attributes). In this case, the PREFIXED rule is active, which prepends a prefix for the namespace of the entity. Simplified this means that <soap12:address>A</soap12:address> becomes soap12_address => A Is there an actual issue you want to have solved?
Subject: Re: [rt.cpan.org #105270] Bug report for WSDL11.pm
Date: Wed, 17 Jun 2015 13:36:35 +0000 (UTC)
To: "bug-XML-Compile-WSDL11 [...] rt.cpan.org" <bug-XML-Compile-WSDL11 [...] rt.cpan.org>
From: Ian Mitchell <mitchell.ianj [...] yahoo.com>
I was unable to parse <soap:address... elements. From: Mark Overmeer via RT <bug-XML-Compile-WSDL11@rt.cpan.org> To: mitchell.ianj@yahoo.com Sent: Wednesday, June 17, 2015 2:12 AM Subject: [rt.cpan.org #105270] Bug report for WSDL11.pm <URL: https://rt.cpan.org/Ticket/Display.html?id=105270 > On Tue Jun 16 11:54:13 2015, mitchell.ianj@yahoo.com wrote: Show quoted text
> > On line 169 of WSDL11.pm, the code contains: > {  my $addr_label = first { /_address$/ } keys %$port > The line should contain: > {  my $addr_label = first { /address$/ } keys %$port > Rational from my perspective: >  WSDL port definitions typically contains "<soap:address...." and the > regular expression used to match the address is expecting a "_" > character, this is causing legitimate address definitions in > wsdl:ports to be ignored.
You are wrong.  XML::Compile supports rewrite rules on names (of elements and attributes).  In this case, the PREFIXED rule is active, which prepends a prefix for the namespace of the entity.  Simplified this means that <soap12:address>A</soap12:address> becomes  soap12_address => A Is there an actual issue you want to have solved?
Subject: Re: [rt.cpan.org #105270] Bug report for WSDL11.pm
Date: Wed, 17 Jun 2015 15:40:31 +0200
To: Ian Mitchell via RT <bug-XML-Compile-WSDL11 [...] rt.cpan.org>
From: Mark Overmeer <mark [...] overmeer.net>
* Ian Mitchell via RT (bug-XML-Compile-WSDL11@rt.cpan.org) [150617 13:37]: Show quoted text
> Queue: XML-Compile-WSDL11 > Ticket <URL: https://rt.cpan.org/Ticket/Display.html?id=105270 > > > I was unable to parse <soap:address... elements.
You get an explicit warning that you will have to load some modules, to support the namespace. For instance, XML::Compile::SOAP11 or ::SOAP12 -- Regards, MarkOv ------------------------------------------------------------------------ Mark Overmeer MSc MARKOV Solutions Mark@Overmeer.net solutions@overmeer.net http://Mark.Overmeer.net http://solutions.overmeer.net
Subject: Re: [rt.cpan.org #105270] Bug report for WSDL11.pm
Date: Wed, 17 Jun 2015 13:52:58 +0000 (UTC)
To: "bug-XML-Compile-WSDL11 [...] rt.cpan.org" <bug-XML-Compile-WSDL11 [...] rt.cpan.org>
From: Ian Mitchell <mitchell.ianj [...] yahoo.com>
I believe that may have been the issue (soap12), but I never received the explicit warning, only that the port element lacked an address. That's what pointed me to that area of the code during a debug run. From: Mark Overmeer via RT <bug-XML-Compile-WSDL11@rt.cpan.org> To: mitchell.ianj@yahoo.com Sent: Wednesday, June 17, 2015 8:41 AM Subject: Re: [rt.cpan.org #105270] Bug report for WSDL11.pm <URL: https://rt.cpan.org/Ticket/Display.html?id=105270 > * Ian Mitchell via RT (bug-XML-Compile-WSDL11@rt.cpan.org) [150617 13:37]: Show quoted text
>        Queue: XML-Compile-WSDL11 >  Ticket <URL: https://rt.cpan.org/Ticket/Display.html?id=105270 > > > I was unable to parse <soap:address... elements.
You get an explicit warning that you will have to load some modules, to support the namespace.  For instance,  XML::Compile::SOAP11 or ::SOAP12 -- Regards,               MarkOv ------------------------------------------------------------------------       Mark Overmeer MSc                                MARKOV Solutions       Mark@Overmeer.net                          solutions@overmeer.net http://Mark.Overmeer.net                   http://solutions.overmeer.net
Subject: Re: [rt.cpan.org #105270] Bug report for WSDL11.pm
Date: Wed, 17 Jun 2015 16:12:55 +0200
To: Ian Mitchell via RT <bug-XML-Compile-WSDL11 [...] rt.cpan.org>
From: Mark Overmeer <mark [...] overmeer.net>
* Ian Mitchell via RT (bug-XML-Compile-WSDL11@rt.cpan.org) [150617 13:54]: Show quoted text
> Queue: XML-Compile-WSDL11 > Ticket <URL: https://rt.cpan.org/Ticket/Display.html?id=105270 > > > I believe that may have been the issue (soap12), but I never received > the explicit warning, only that the port element lacked an address. That's > what pointed me to that area of the code during a debug run.
Thank you for pushing this further: I think there is a problem with that piece of the code. I am sure I have seen it work, but at the moment there seems to be a problem with the order of the checks. Probably because I have moved the location where internal namespace prefixes get loaded. I'll fix that. -- Regards, MarkOv ------------------------------------------------------------------------ Mark Overmeer MSc MARKOV Solutions Mark@Overmeer.net solutions@overmeer.net http://Mark.Overmeer.net http://solutions.overmeer.net