facebook

Web Services Explorer Suggestions

  1. MyEclipse Archived
  2.  > 
  3. Web Services
Viewing 4 posts - 1 through 4 (of 4 total)
  • Author
    Posts
  • #255911 Reply

    jkristian
    Member

    Some suggestions for improving the Web Services Explorer:

    In the Navigator (left) pane, make the [Delete] key delete the currently selected item.

    Generally, work as well as <a href=”http://www.soapui.org/”>SoapUI</a&gt;.

    #255912 Reply

    jkristian
    Member

    Create multiple endpoints from WSDL. For example, this WSDL should produce 5 endpoints (one for each wsdl:port):

    <?xml version="1.0" encoding="UTF-8"?>
    <wsdl:definitions xmlns:wsdl="http://schemas.xmlsoap.org/wsdl/" xmlns:soap11="http://schemas.xmlsoap.org/soap/envelope/" xmlns:soap12="http://www.w3.org/2003/05/soap-envelope" xmlns:soapenc11="http://schemas.xmlsoap.org/soap/encoding/" xmlns:soapenc12="http://www.w3.org/2003/05/soap-encoding" xmlns:tns="http://webservice.netflix.com/CustomerData/SOAP-1.0" xmlns:wsdlsoap="http://schemas.xmlsoap.org/wsdl/soap/" xmlns:xsd="http://www.w3.org/2001/XMLSchema" targetNamespace="http://webservice.netflix.com/CustomerData/SOAP-1.0">
      <wsdl:types>
        <xsd:schema targetNamespace="http://webservice.netflix.com/CustomerData/SOAP-1.0" elementFormDefault="qualified" attributeFormDefault="qualified">
          <xsd:element name="echo">
            <xsd:complexType>
              <xsd:sequence>
                <xsd:element name="data" type="xsd:string" nillable="true" minOccurs="1" maxOccurs="1" />
              </xsd:sequence>
            </xsd:complexType>
          </xsd:element>
          <xsd:element name="echoResponse">
            <xsd:complexType>
              <xsd:sequence>
                <xsd:element name="out" type="xsd:string" nillable="true" minOccurs="1" maxOccurs="1" />
              </xsd:sequence>
            </xsd:complexType>
          </xsd:element>
        </xsd:schema>
      </wsdl:types>
      <wsdl:message name="echoRequest">
        <wsdl:part element="tns:echo" name="parameters" />
      </wsdl:message>
      <wsdl:message name="echoResponse">
        <wsdl:part element="tns:echoResponse" name="parameters" />
      </wsdl:message>
      <wsdl:portType name="SOAP">
        <wsdl:operation name="echo">
          <wsdl:input message="tns:echoRequest" name="echoRequest" />
          <wsdl:output message="tns:echoResponse" name="echoResponse" />
        </wsdl:operation>
      </wsdl:portType>
      <wsdl:binding name="Binding" type="tns:SOAP">
        <wsdlsoap:binding style="document" transport="http://schemas.xmlsoap.org/soap/http" />
        <wsdl:operation name="echo">
          <wsdlsoap:operation soapAction="" />
          <wsdl:input name="echoRequest">
            <wsdlsoap:body use="literal" />
          </wsdl:input>
          <wsdl:output name="echoResponse">
            <wsdlsoap:body use="literal" />
          </wsdl:output>
        </wsdl:operation>
      </wsdl:binding>
      <wsdl:service name="SOAP-1.0">
        <wsdl:port binding="tns:Binding" name="Dev">
          <wsdlsoap:address location="https://cdsdev.netflix.com:7002/webservice/CustomerData/SOAP-1.0" />
        </wsdl:port>
        <wsdl:port binding="tns:Binding" name="Secondary">
          <wsdlsoap:address location="https://cds-secondary.netflix.com:7002/webservice/CustomerData/SOAP-1.0" />
        </wsdl:port>
        <wsdl:port binding="tns:Binding" name="JKristian">
          <wsdlsoap:address location="http://lg01-jkristian.netflix.com/webservice/CustomerData/SOAP-1.0" />
        </wsdl:port>
        <wsdl:port binding="tns:Binding" name="Test">
          <wsdlsoap:address location="https://cdstest.netflix.com:7002/webservice/CustomerData/SOAP-1.0" />
        </wsdl:port>
        <wsdl:port binding="tns:Binding" name="Primary">
          <wsdlsoap:address location="https://cds-primary.netflix.com:7002/webservice/CustomerData/SOAP-1.0" />
        </wsdl:port>
      </wsdl:service>
    </wsdl:definitions>
    #255914 Reply

    jkristian
    Member

    Retain WSDL, so it’s readily available for re-use. (The current explorer forgets WSDL when I close the Explorer and restart Eclipse.)

    #255961 Reply

    jkristian
    Member

    Pool your resources with the SoapUI eclipse-plugin project, to combine the best features of SoapUI and MyEclipse. Don’t beat them; join them.
    http://www.soapui.org/eclipse/index.html

Viewing 4 posts - 1 through 4 (of 4 total)
Reply To: Web Services Explorer Suggestions

You must be logged in to post in the forum log in