Bug: Sending WSDL request using repeatable section
Description
When executing a web service (WSDL) data connection, only the last instance of a repeatable element is included in the request.
Here’s an example of a repeatable WSDL element (the “Detail” element containing item number information):
<xsd:element name="Details">
<xsd:complexType>
<xsd:sequence>
<xsd:element name="Detail" maxOccurs="unbounded">
<xsd:complexType>
<xsd:sequence>
<xsd:element name="ItemNumber" type="xsd:string"/>
</xsd:sequence>
</xsd:complexType>
</xsd:element>
</xsd:sequence>
</xsd:complexType>
</xsd:element>The correct behaviour is that all instances of a repeatable section are used in the request sent to the web service.
Workaround
Unfortunately, there are no workarounds for this problem however the bug will be fixed in the next release of Acrobat.
Fix
Please refer to the Bug List for updated information on the version(s) affected by this bug as well as if and when it was/will be fixed.
Posted by Stefan Cameron on May 2nd, 2007
Filed under Acrobat, Bugs
You can skip to the end and leave a response. Pinging is currently not allowed.
Stefan,
I encountered this bug a few months ago, and found your reference to it. I’d like to let you know that Acrobat Professional 8.1.0 has the bug fixed and correctly sends ALL instances of repeatable sections. This note, is just so you can update the FIX ilne on the buglist.
Thanks for keeping track of these obnoxious bugs.
Jeremy.
Jeremy Zellers,
Thanks for pointing this out and helping me keep my Bug List up-to-date. I’m glad you find it useful!
Stefan,
Could you show me the code for your echoEmployee webmethod? I am having troubles returning a dataset as you have done in this example.
Thanks in advance,
Jake
Jake Long,
I’m afraid the echoEmployee service/method isn’t mine. It’s just a web service that’s available on the web which I used to demonstrate connecting to web services in an XFA form.