Subject: | Interface-Operation POD template does not handle empty method replies |
Hi,
I think I have identified an issue where Interface/POD/Operation.tt
fails to work against methods whose reply messages don't contain any
fields.
For example, I am working against
https://provisioning.fetchtv.com.au/provisioning/ws/service.wsdl which
defines a method response element like this:
<xsd:element name="activateTerminalResponse"
type="tns:activateTerminalResponse" />
When generating POD documentation, Operation.tt tries to load the first
response part and document it, If there is no first response part
because the message is empty, an error such as 'undef error - no node'
occurs as the template tries to access it.
The attached file fixes the problem by handling the case of a method
reply which contains no parts. It tests the first member of the parts
array and documents the method response as empty if the part is not
present.
I am running perl v5.8.8 on Debian with CPAN's current version of
SOAP::WSDL (2.00.10)
Subject: | Operation.tt |
Message body not shown because it is not plain text.