Forum Discussion

Victor_Perez_Su's avatar
Victor_Perez_Su
Occasional Contributor
15 years ago

[Resolved] Form View and unbounded elements

The Form view does not handle xml sequences that contain elements with maxOccurs="unbounded". I do not get the Add/Delete buttons in the form view that will allow me to add new elements to the array.

Here is a sample from my WSDL:

<s:schema elementFormDefault="qualified" targetNamespace="http://www.test.com/XMLSchema">
   <s:element name="VerificationRequest" type="s1:VerificationRequestType"/>
   <s:complexType name="VerificationRequestType">
      <s:sequence>
         <s:element minOccurs="0" maxOccurs="unbounded" name="Verification" type="s1:VerificationType"/>
      </s:sequence>
      <s:attribute name="Platform" type="s:string"/>
   </s:complexType>
   <s:complexType name="VerificationType">
      <s:attribute name="VerificationID" type="s:long" use="required"/>
      <s:attribute name="MaterialChangeDate" type="s:dateTime" use="required"/>
   </s:complexType>
 </s:schema>


This is what the Form View looks like: (notice the red circle where the Add/Delete buttons should be)


I believe that the Form View is missing the Add/Delete buttons for unbounded elements. This issue makes its very hard for my group to use this software. The only workaround we have found is to switch to the XML tab and copy and paste each xml element. This is very time consuming because most of our other webservice requests have 50 or more elements. The example I have included is the simplest case.

If you have any questions, please let me know.

13 Replies

  • Victor_Perez_Su's avatar
    Victor_Perez_Su
    Occasional Contributor
    15 years ago
    I have sent an email to support with an attached WSDL. Reference: #LLG-867218.

    For anyone else who may want to test this issue, here is the WSDL that reproduces the issue.


    <?xml version="1.0" encoding="UTF-8"?>
    <wsdl:definitions targetNamespace="http://www.test.com/WebServices" xmlns:soap="http://schemas.xmlsoap.org/wsdl/soap/" xmlns:tm="http://microsoft.com/wsdl/mime/textMatching/" xmlns:soapenc="http://schemas.xmlsoap.org/soap/encoding/" xmlns:mime="http://schemas.xmlsoap.org/wsdl/mime/" xmlns:tns="http://www.test.com/WebServices" xmlns:s1="http://www.test.com/XMLSchema" xmlns:s="http://www.w3.org/2001/XMLSchema" xmlns:soap12="http://schemas.xmlsoap.org/wsdl/soap12/" xmlns:http="http://schemas.xmlsoap.org/wsdl/http/" xmlns:wsdl="http://schemas.xmlsoap.org/wsdl/">
      <wsdl:types>
        <s:schema elementFormDefault="qualified" targetNamespace="http://www.test.com/WebServices">
          <s:import namespace="http://www.test.com/XMLSchema"/>
          <s:element name="Verification">
            <s:complexType>
              <s:sequence>
                <s:element minOccurs="0" maxOccurs="1" ref="s1:VerificationRequest"/>
              </s:sequence>
            </s:complexType>
          </s:element>
          <s:element name="VerificationResponse">
            <s:complexType>
              <s:sequence>
                <s:element minOccurs="1" maxOccurs="1" name="VerificationResult" type="s:boolean"/>
              </s:sequence>
            </s:complexType>
          </s:element>
        </s:schema>
        <s:schema elementFormDefault="qualified" targetNamespace="http://www.test.com/XMLSchema">
          <s:element name="VerificationRequest" type="s1:VerificationRequestType"/>
          <s:complexType name="VerificationRequestType">
            <s:sequence>
              <s:element minOccurs="0" maxOccurs="1" name="VerificationList" type="s1:ArrayOfVerificationType"/>
            </s:sequence>
            <s:attribute name="Platform" type="s:string"/>
          </s:complexType>
          <s:complexType name="ArrayOfVerificationType">
            <s:sequence>
              <s:element minOccurs="0" maxOccurs="unbounded" name="Verification" type="s1:VerificationType"/>
            </s:sequence>
          </s:complexType>
          <s:complexType name="VerificationType">
            <s:attribute name="VerificationID" type="s:long" use="required"/>
            <s:attribute name="MaterialChangeDate" type="s:dateTime" use="required"/>
          </s:complexType>
        </s:schema>
      </wsdl:types>
      <wsdl:message name="VerificationSoapIn">
        <wsdl:part name="parameters" element="tns:Verification"/>
      </wsdl:message>
      <wsdl:message name="VerificationSoapOut">
        <wsdl:part name="parameters" element="tns:VerificationResponse"/>
      </wsdl:message>
      <wsdl:portType name="VerificationOnTransferSoap">
        <wsdl:operation name="Verification">
          <wsdl:documentation>Verification</wsdl:documentation>
          <wsdl:input message="tns:VerificationSoapIn"/>
          <wsdl:output message="tns:VerificationSoapOut"/>
        </wsdl:operation>
      </wsdl:portType>
      <wsdl:binding name="VerificationOnTransferSoap" type="tns:VerificationOnTransferSoap">
        <soap:binding transport="http://schemas.xmlsoap.org/soap/http"/>
        <wsdl:operation name="Verification">
          <soap:operation soapAction="http://www.test.com/WebServices/Verification" style="document"/>
          <wsdl:input>
            <soap:body use="literal"/>
          </wsdl:input>
          <wsdl:output>
            <soap:body use="literal"/>
          </wsdl:output>
        </wsdl:operation>
      </wsdl:binding>
      <wsdl:binding name="VerificationOnTransferSoap12" type="tns:VerificationOnTransferSoap">
        <soap12:binding transport="http://schemas.xmlsoap.org/soap/http"/>
        <wsdl:operation name="Verification">
          <soap12:operation soapAction="http://www.test.com/WebServices/Verification" style="document"/>
          <wsdl:input>
            <soap12:body use="literal"/>
          </wsdl:input>
          <wsdl:output>
            <soap12:body use="literal"/>
          </wsdl:output>
        </wsdl:operation>
      </wsdl:binding>
      <wsdl:service name="VerificationOnTransfer">
        <wsdl:port name="VerificationOnTransferSoap" binding="tns:VerificationOnTransferSoap">
          <soap:address location="http://localhost/WebServices/VerificationOnTransfer.asmx"/>
        </wsdl:port>
        <wsdl:port name="VerificationOnTransferSoap12" binding="tns:VerificationOnTransferSoap12">
          <soap12:address location="http://localhost/WebServices/VerificationOnTransfer.asmx"/>
        </wsdl:port>
      </wsdl:service>
    </wsdl:definitions>
  • Victor_Perez_Su's avatar
    Victor_Perez_Su
    Occasional Contributor
    15 years ago
    Is there any update on this issue? Were you able to reproduce the problem with my WSDL?
  • CARQUESTTechnol's avatar
    CARQUESTTechnol
    Contributor
    15 years ago
    Is there any update on this? I have a support ticket HON-734688 and FIV-479154 open on this issue. I'm getting lots of complaints about this defect internally from our dev and test team.
  • SmartBear_Suppo's avatar
    SmartBear_Suppo
    Icon for Alumni rankAlumni
    15 years ago
    Hi,

    sorry for the delay on this, we're still trying to figure it out.. will let you know as soon as possible!

    regards,

    /Ole
    eviware.com
  • CARQUESTTechnol's avatar
    CARQUESTTechnol
    Contributor
    14 years ago
    Can I at least ask can you reproduce it? And where is this on your list of priorities. Users of the tool get mad at me when their requests are getting wiped out.
  • CARQUESTTechnol's avatar
    CARQUESTTechnol
    Contributor
    14 years ago
    Hello? This is an issue in which many of the users of Pro are complaining about in our organization. Has this been reproduced? Is this the support that we are getting for our money?
  • SmartBear_Suppo's avatar
    SmartBear_Suppo
    Icon for Alumni rankAlumni
    14 years ago
    Hello,

    we are very sorry for the delay on this issue, it is definitely more complex than we anticipated and will hopefully be sorted out within the coming weeks. We will post back here as soon as we have something for you to try out.

    best regards,

    /Ole
    eviware.com
  • Victor_Perez_Su's avatar
    Victor_Perez_Su
    Occasional Contributor
    14 years ago
    Has there been any update on this issue? I am getting constant complaints from my users. It has been almost 3 months since the last update from eviware. Your website says
    At eviware we strive for offering world class support.
    To be honest, I feel like this is not being treated with a high enough importance. I would expect "world class support" to at least inform their customers about the status of an issue.

    Can we please have an update with an approximate timeline for when the fix will be completed?
  • SmartBear_Suppo's avatar
    SmartBear_Suppo
    Icon for Alumni rankAlumni
    14 years ago
    Hi Victor,

    you are totally right, we've really screwed up on this support issue - and I'm very sorry about failing you guys here. All our efforts are currently on the 4.0 beta1 release next week, but our ambition is still to have this (and some other long overlooked bugs) fixed for the final 4.0 release in mid June. When the fix is available in a nightly build, I will be sure to let you know here on the forum.

    Sorry again,

    regards,

    /Ole
    eviware.com