Loading ...
Sorry, an error occurred while loading the content.

multipartRelated does not compile

Expand Messages
  • bsrobert_cv
    Hello, I am trying to compile this simple WSDL file using : - .NET through wsdl.exe - JWSDP 1.3 through wscompile finally, it works with WSDL2Java (Axis)
    Message 1 of 5 , Apr 22, 2004
    • 0 Attachment
      Hello,

      I am trying to compile this simple WSDL file using :
      - .NET through wsdl.exe
      - JWSDP 1.3 through wscompile

      finally, it works with WSDL2Java (Axis)

      Attachment APIs work fine using SAAJ, and handlers but
      the WSDL contract is more important for me than APIs.

      I would like to know if
      WS-I Attachments Profile V1.0
      has already been implemented in wsdl.exe (.NET) and JWSDP 1.3
      By the way, the error that I get when compiling in both .NET and JWSDP
      is : <<Missing soap:body input binding.>>

      Thanks,
      Brice

      <wsdl:definitions
      name="urn:ALS/CAL/SoapService"
      targetNamespace="urn:ALS/CAL/SoapService"
      xmlns:tns="urn:ALS/CAL/SoapService"
      xmlns:typens="urn:ALS/CAL/SoapService"
      xmlns:xsd="http://www.w3.org/2001/XMLSchema"
      xmlns:soap="http://schemas.xmlsoap.org/wsdl/soap/"
      xmlns:soapenc="http://schemas.xmlsoap.org/soap/encoding/"
      xmlns:mime="http://schemas.xmlsoap.org/wsdl/mime/"
      xmlns:wsdl="http://schemas.xmlsoap.org/wsdl/"
      >

      <wsdl:message name="msg-in">
      <wsdl:part name="photo-reference" type="xsd:anyURI"/>
      <wsdl:part name="photo-attachment" type="xsd:base64Binary"/>
      </wsdl:message>

      <wsdl:message name="msg-out">
      <wsdl:part name="result" type="xsd:string"/>
      </wsdl:message>

      <wsdl:portType name="my-portType">
      <wsdl:operation name="my-operation">
      <wsdl:input message="tns:msg-in"/>
      <wsdl:output message="tns:msg-out"/>
      </wsdl:operation>
      </wsdl:portType>

      <wsdl:binding name="my-binding" type="tns:my-portType">
      <soap:binding style="rpc"
      transport="http://schemas.xmlsoap.org/soap/http"/>
      <wsdl:operation name="my-operation">
      <soap:operation soapAction="http://example.com/soapaction"/>
      <wsdl:input>
      <mime:multipartRelated>
      <mime:part>
      <soap:body use="literal" />
      </mime:part>
      <mime:part>
      <mime:content part="photo-attachment"
      type="application/octetstream"/>
      </mime:part>
      </mime:multipartRelated>
      </wsdl:input>
      <wsdl:output>
      <mime:multipartRelated>
      <mime:part>
      <soap:body parts="photo-reference" use="literal"
      />
      </mime:part>
      <mime:part>
      <mime:content part="photo-attachment"
      type="application/octetstream"/>
      </mime:part>
      </mime:multipartRelated>
      </wsdl:output>
      </wsdl:operation>
      </wsdl:binding>
      <!-- service decln -->
      <wsdl:service name="TranslationService">
      <wsdl:port name="TranslationPort" binding="tns:my-binding">
      <soap:address location="http://example.com/services/documents"/>
      </wsdl:port>
      </wsdl:service>


      </wsdl:definitions>
    • Doug Kohlert
      Brice, WS-I Attachment Profile 1.0 will be implemented in JWSDP 1.4 due out in the next month or so. ... --
      Message 2 of 5 , Apr 22, 2004
      • 0 Attachment
        Brice,
        WS-I Attachment Profile 1.0 will be implemented in JWSDP 1.4 due out in
        the next month or so.

        bsrobert_cv wrote:

        >Hello,
        >
        >I am trying to compile this simple WSDL file using :
        >- .NET through wsdl.exe
        >- JWSDP 1.3 through wscompile
        >
        >finally, it works with WSDL2Java (Axis)
        >
        >Attachment APIs work fine using SAAJ, and handlers but
        >the WSDL contract is more important for me than APIs.
        >
        >I would like to know if
        >WS-I Attachments Profile V1.0
        >has already been implemented in wsdl.exe (.NET) and JWSDP 1.3
        >By the way, the error that I get when compiling in both .NET and JWSDP
        >is : <<Missing soap:body input binding.>>
        >
        >Thanks,
        >Brice
        >
        ><wsdl:definitions
        > name="urn:ALS/CAL/SoapService"
        > targetNamespace="urn:ALS/CAL/SoapService"
        > xmlns:tns="urn:ALS/CAL/SoapService"
        > xmlns:typens="urn:ALS/CAL/SoapService"
        > xmlns:xsd="http://www.w3.org/2001/XMLSchema"
        > xmlns:soap="http://schemas.xmlsoap.org/wsdl/soap/"
        > xmlns:soapenc="http://schemas.xmlsoap.org/soap/encoding/"
        > xmlns:mime="http://schemas.xmlsoap.org/wsdl/mime/"
        > xmlns:wsdl="http://schemas.xmlsoap.org/wsdl/"
        > >
        >
        ><wsdl:message name="msg-in">
        > <wsdl:part name="photo-reference" type="xsd:anyURI"/>
        > <wsdl:part name="photo-attachment" type="xsd:base64Binary"/>
        ></wsdl:message>
        >
        ><wsdl:message name="msg-out">
        > <wsdl:part name="result" type="xsd:string"/>
        ></wsdl:message>
        >
        ><wsdl:portType name="my-portType">
        > <wsdl:operation name="my-operation">
        > <wsdl:input message="tns:msg-in"/>
        > <wsdl:output message="tns:msg-out"/>
        > </wsdl:operation>
        ></wsdl:portType>
        >
        ><wsdl:binding name="my-binding" type="tns:my-portType">
        > <soap:binding style="rpc"
        >transport="http://schemas.xmlsoap.org/soap/http"/>
        > <wsdl:operation name="my-operation">
        > <soap:operation soapAction="http://example.com/soapaction"/>
        > <wsdl:input>
        > <mime:multipartRelated>
        > <mime:part>
        > <soap:body use="literal" />
        > </mime:part>
        > <mime:part>
        > <mime:content part="photo-attachment"
        >type="application/octetstream"/>
        > </mime:part>
        > </mime:multipartRelated>
        > </wsdl:input>
        > <wsdl:output>
        > <mime:multipartRelated>
        > <mime:part>
        > <soap:body parts="photo-reference" use="literal"
        >/>
        > </mime:part>
        > <mime:part>
        > <mime:content part="photo-attachment"
        > type="application/octetstream"/>
        > </mime:part>
        > </mime:multipartRelated>
        > </wsdl:output>
        > </wsdl:operation>
        > </wsdl:binding>
        > <!-- service decln -->
        > <wsdl:service name="TranslationService">
        > <wsdl:port name="TranslationPort" binding="tns:my-binding">
        > <soap:address location="http://example.com/services/documents"/>
        > </wsdl:port>
        > </wsdl:service>
        >
        >
        ></wsdl:definitions>
        >
        >
        >
        >
        >
        >-----------------------------------------------------------------
        >This group is a forum for builders of SOAP implementations to discuss implementation and interoperability issues. Please stay on-topic.
        >Yahoo! Groups Links
        >
        >
        >
        >
        >
        >
        >

        --
        ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
        Doug Kohlert

        Sun Microsystems, Inc.
        doug.kohlert@...
        ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
      • George Rusev
        Hi, I am not sure that this WSDL will compile in .NET ever, as they support DIME attachments while others support MIME Regards, George Rusev ...
        Message 3 of 5 , Apr 23, 2004
        • 0 Attachment
          Hi,

          I am not sure that this WSDL will compile in .NET
          ever, as they support DIME attachments while others
          support MIME

          Regards,
          George Rusev

          --- bsrobert_cv <bsrobert_cv@...> wrote:
          > Hello,
          >
          > I am trying to compile this simple WSDL file using :
          > - .NET through wsdl.exe
          > - JWSDP 1.3 through wscompile
          >
          > finally, it works with WSDL2Java (Axis)
          >
          > Attachment APIs work fine using SAAJ, and handlers
          > but
          > the WSDL contract is more important for me than
          > APIs.
          >
          > I would like to know if
          > WS-I Attachments Profile V1.0
          > has already been implemented in wsdl.exe (.NET) and
          > JWSDP 1.3
          > By the way, the error that I get when compiling in
          > both .NET and JWSDP
          > is : <<Missing soap:body input binding.>>
          >
          > Thanks,
          > Brice
          >
          > <wsdl:definitions
          > name="urn:ALS/CAL/SoapService"
          > targetNamespace="urn:ALS/CAL/SoapService"
          > xmlns:tns="urn:ALS/CAL/SoapService"
          > xmlns:typens="urn:ALS/CAL/SoapService"
          > xmlns:xsd="http://www.w3.org/2001/XMLSchema"
          >
          > xmlns:soap="http://schemas.xmlsoap.org/wsdl/soap/"
          >
          >
          xmlns:soapenc="http://schemas.xmlsoap.org/soap/encoding/"
          >
          >
          > xmlns:mime="http://schemas.xmlsoap.org/wsdl/mime/"
          > xmlns:wsdl="http://schemas.xmlsoap.org/wsdl/"
          > >
          >
          > <wsdl:message name="msg-in">
          > <wsdl:part name="photo-reference"
          > type="xsd:anyURI"/>
          > <wsdl:part name="photo-attachment"
          > type="xsd:base64Binary"/>
          > </wsdl:message>
          >
          > <wsdl:message name="msg-out">
          > <wsdl:part name="result" type="xsd:string"/>
          > </wsdl:message>
          >
          > <wsdl:portType name="my-portType">
          > <wsdl:operation name="my-operation">
          > <wsdl:input message="tns:msg-in"/>
          > <wsdl:output message="tns:msg-out"/>
          > </wsdl:operation>
          > </wsdl:portType>
          >
          > <wsdl:binding name="my-binding"
          > type="tns:my-portType">
          > <soap:binding style="rpc"
          > transport="http://schemas.xmlsoap.org/soap/http"/>
          > <wsdl:operation name="my-operation">
          > <soap:operation
          > soapAction="http://example.com/soapaction"/>
          > <wsdl:input>
          > <mime:multipartRelated>
          > <mime:part>
          > <soap:body use="literal" />
          > </mime:part>
          > <mime:part>
          > <mime:content
          > part="photo-attachment"
          > type="application/octetstream"/>
          > </mime:part>
          > </mime:multipartRelated>
          > </wsdl:input>
          > <wsdl:output>
          > <mime:multipartRelated>
          > <mime:part>
          > <soap:body
          > parts="photo-reference" use="literal"
          > />
          > </mime:part>
          > <mime:part>
          > <mime:content
          > part="photo-attachment"
          >
          > type="application/octetstream"/>
          > </mime:part>
          > </mime:multipartRelated>
          > </wsdl:output>
          > </wsdl:operation>
          > </wsdl:binding>
          > <!-- service decln -->
          > <wsdl:service name="TranslationService">
          > <wsdl:port name="TranslationPort"
          > binding="tns:my-binding">
          > <soap:address
          > location="http://example.com/services/documents"/>
          > </wsdl:port>
          > </wsdl:service>
          >
          >
          > </wsdl:definitions>
          >
          >
          >





          __________________________________
          Do you Yahoo!?
          Yahoo! Photos: High-quality 4x6 digital prints for 25�
          http://photos.yahoo.com/ph/print_splash
        • bsrobert_cv
          Doug, Georges, Two answers in one: - Doug, thanks for the info on JWSDP1.4 release - Georges, I think MS will have to implement MIME they were part of WSDL1.1
          Message 4 of 5 , Apr 23, 2004
          • 0 Attachment
            Doug, Georges,

            Two answers in one:

            - Doug, thanks for the info on JWSDP1.4 release
            - Georges, I think MS will have to implement MIME they
            were part of WSDL1.1 specification and (SwA) SOAP Messages with
            Attachments. It might be a question of time.

            Brice,

            Ref:
            * Attachments Profile Version 1.0
            http://www.ws-i.org/Profiles/Basic/2003-08/AttachmentsProfile-1.0.htm

            * SOAP Messages with Attachments
            http://www.w3.org/TR/SOAP-attachments
            * WSDL 1.1, Section 5.0
            http://www.w3.org/TR/wsdl#_Toc492291084

            --- In soapbuilders@yahoogroups.com, George Rusev <george_rusev@y...>
            wrote:
            > Hi,
            >
            > I am not sure that this WSDL will compile in .NET
            > ever, as they support DIME attachments while others
            > support MIME
            >
            > Regards,
            > George Rusev
            >
            > --- bsrobert_cv <bsrobert_cv@y...> wrote:
            > > Hello,
            > >
            > > I am trying to compile this simple WSDL file using :
            > > - .NET through wsdl.exe
            > > - JWSDP 1.3 through wscompile
            > >
            > > finally, it works with WSDL2Java (Axis)
            > >
            > > Attachment APIs work fine using SAAJ, and handlers
            > > but
            > > the WSDL contract is more important for me than
            > > APIs.
            > >
            > > I would like to know if
            > > WS-I Attachments Profile V1.0
            > > has already been implemented in wsdl.exe (.NET) and
            > > JWSDP 1.3
            > > By the way, the error that I get when compiling in
            > > both .NET and JWSDP
            > > is : <<Missing soap:body input binding.>>
            > >
            > > Thanks,
            > > Brice
            > >
            > > <wsdl:definitions
            > > name="urn:ALS/CAL/SoapService"
            > > targetNamespace="urn:ALS/CAL/SoapService"
            > > xmlns:tns="urn:ALS/CAL/SoapService"
            > > xmlns:typens="urn:ALS/CAL/SoapService"
            > > xmlns:xsd="http://www.w3.org/2001/XMLSchema"
            > >
            > > xmlns:soap="http://schemas.xmlsoap.org/wsdl/soap/"
            > >
            > >
            > xmlns:soapenc="http://schemas.xmlsoap.org/soap/encoding/"
            > >
            > >
            > > xmlns:mime="http://schemas.xmlsoap.org/wsdl/mime/"
            > > xmlns:wsdl="http://schemas.xmlsoap.org/wsdl/"
            > > >
            > >
            > > <wsdl:message name="msg-in">
            > > <wsdl:part name="photo-reference"
            > > type="xsd:anyURI"/>
            > > <wsdl:part name="photo-attachment"
            > > type="xsd:base64Binary"/>
            > > </wsdl:message>
            > >
            > > <wsdl:message name="msg-out">
            > > <wsdl:part name="result" type="xsd:string"/>
            > > </wsdl:message>
            > >
            > > <wsdl:portType name="my-portType">
            > > <wsdl:operation name="my-operation">
            > > <wsdl:input message="tns:msg-in"/>
            > > <wsdl:output message="tns:msg-out"/>
            > > </wsdl:operation>
            > > </wsdl:portType>
            > >
            > > <wsdl:binding name="my-binding"
            > > type="tns:my-portType">
            > > <soap:binding style="rpc"
            > > transport="http://schemas.xmlsoap.org/soap/http"/>
            > > <wsdl:operation name="my-operation">
            > > <soap:operation
            > > soapAction="http://example.com/soapaction"/>
            > > <wsdl:input>
            > > <mime:multipartRelated>
            > > <mime:part>
            > > <soap:body use="literal" />
            > > </mime:part>
            > > <mime:part>
            > > <mime:content
            > > part="photo-attachment"
            > > type="application/octetstream"/>
            > > </mime:part>
            > > </mime:multipartRelated>
            > > </wsdl:input>
            > > <wsdl:output>
            > > <mime:multipartRelated>
            > > <mime:part>
            > > <soap:body
            > > parts="photo-reference" use="literal"
            > > />
            > > </mime:part>
            > > <mime:part>
            > > <mime:content
            > > part="photo-attachment"
            > >
            > > type="application/octetstream"/>
            > > </mime:part>
            > > </mime:multipartRelated>
            > > </wsdl:output>
            > > </wsdl:operation>
            > > </wsdl:binding>
            > > <!-- service decln -->
            > > <wsdl:service name="TranslationService">
            > > <wsdl:port name="TranslationPort"
            > > binding="tns:my-binding">
            > > <soap:address
            > > location="http://example.com/services/documents"/>
            > > </wsdl:port>
            > > </wsdl:service>
            > >
            > >
            > > </wsdl:definitions>
            > >
            > >
            > >
            >
            >
            >
            >
            >
            > __________________________________
            > Do you Yahoo!?
            > Yahoo! Photos: High-quality 4x6 digital prints for 25¢
            > http://photos.yahoo.com/ph/print_splash
          • Rich Salz
            ... Microsoft has said: DIME is dead. The MIME-based paswa , or SOAP w/Attachments, approach, is the way forward. They may not have released code that
            Message 5 of 5 , Apr 23, 2004
            • 0 Attachment
              > I am not sure that this WSDL will compile in .NET
              > ever, as they support DIME attachments while others
              > support MIME

              Microsoft has said: DIME is dead. The MIME-based "paswa", or SOAP
              w/Attachments, approach, is the way forward.

              They may not have released code that supports this yet.
              /r$
              --
              Rich Salz, Chief Security Architect
              DataPower Technology http://www.datapower.com
              XS40 XML Security Gateway http://www.datapower.com/products/xs40.html
              XML Security Overview http://www.datapower.com/xmldev/xmlsecurity.html
            Your message has been successfully submitted and would be delivered to recipients shortly.