RE: BizTalk mulitpart Error when communicating with an Axis service

Patrick Quinn Tue, 12 Jul 2005 02:47:18 -0700

Title: Message

Just to clarify (and with a particular apology to Anne!), I have posted this question before - but the customer I deal with gave misleading information about where the error was seen.

The WSDL and WSDD are included below for anyone who might be able to spare the time to look at this.

I notice that the error:

" Provident Connector Send: Exception invoking WS... The XLANG/s message has no part at index '0'. The total number of parts found in the message is '0'. If you expect a multipart message, check that the pipeline supports multipart messages such as MIME. "

mentions multipart, and that I am also seeing a multipart warning in my Axis environment:

"Unable to find required classes (javax.activation.DataHandler and javax.mail.internet.MimeMultipart). Attachment support is disabled."

I have searched around the forum and the web for more information on this warning, but all I have found is a suggestion that it is not important. Oddly, activation.jar is in my classpath and yet I still get this javax.activation.DataHandler warning - but this is the jar file containing the class?!

Patrick

wsdl

<?xml version="1.0" encoding="utf-8"?>
<wsdl:definitions xmlns:s1="http://ProvidentConnector.ProvidentResponseToOrch" xmlns:http="http://schemas.xmlsoap.
org/wsdl/http/" xmlns:soap="http://schemas.xmlsoap.org/wsdl/soap/" xmlns:s="http://www.w3.org/2001/XMLSchema" xmln
s:soapenc="http://schemas.xmlsoap.org/soap/encoding/" xmlns:tns="http://namespace.accenture.com/" xmlns:tm="http:/
/microsoft.com/wsdl/mime/textMatching/" xmlns:mime="http://schemas.xmlsoap.org/wsdl/mime/" targetNamespace="http:/
/namespace.accenture.com/" xmlns:wsdl="http://schemas.xmlsoap.org/wsdl/">
<wsdl:types>
    <s:schema elementFormDefault="qualified" targetNamespace="http://namespace.accenture.com/">
      <s:import namespace="http://ProvidentConnector.ProvidentResponseToOrch" />
      <s:element name="SOPResponse">
        <s:complexType>
          <s:sequence>
            <s:element minOccurs="0" maxOccurs="1" ref="s1:ProvidentResponse" />
          </s:sequence>
        </s:complexType>
      </s:element>
      <s:element name="SOPResponseResponse">
        <s:complexType>
          <s:sequence>
            <s:element minOccurs="0" maxOccurs="1" name="part" type="s:string" />
          </s:sequence>
        </s:complexType>
      </s:element>
    </s:schema>
    <s:schema elementFormDefault="qualified" targetNamespace="http://ProvidentConnector.ProvidentResponseToOrch">
      <s:element name="ProvidentResponse" type="s1:ProvidentResponse" />
      <s:complexType name="ProvidentResponse">
        <s:sequence>
          <s:element minOccurs="0" maxOccurs="1" form="unqualified" name="REQUESTID" type="s:string" />
          <s:element minOccurs="0" maxOccurs="1" form="unqualified" name="SO_RESULT_CODE" type="s:string" />
          <s:element minOccurs="0" maxOccurs="1" form="unqualified" name="SO_PROV_DATE" type="s:string" />
          <s:element minOccurs="0" maxOccurs="1" form="unqualified" name="SO_ERR_DESC" type="s:string" />
          <s:element minOccurs="0" maxOccurs="1" form="unqualified" name="XML_SORESULT" type="s:string" />
        </s:sequence>
      </s:complexType>
    </s:schema>
</wsdl:types>
<wsdl:message name="SOPResponseSoapIn">
    <wsdl:part name="parameters" element="tns:SOPResponse" />
</wsdl:message>
<wsdl:message name="SOPResponseSoapOut">
    <wsdl:part name="parameters" element="tns:SOPResponseResponse" />
</wsdl:message>
<wsdl:portType name="ProvidentConnector_ProvidentReceiver_ProvidentWSPortSoap">
    <wsdl:operation name="SOPResponse">
      <wsdl:input message="tns:SOPResponseSoapIn" />
      <wsdl:output message="tns:SOPResponseSoapOut" />
    </wsdl:operation>
</wsdl:portType>
<wsdl:binding name="ProvidentConnector_ProvidentReceiver_ProvidentWSPortSoap" type="tns:ProvidentConnector_ProvidentReceiver_ProvidentWSPortSoap">
    <soap:binding transport="http://schemas.xmlsoap.org/soap/http" style="document" />
    <wsdl:operation name="SOPResponse">
      <soap:operation soapAction="http://namespace.accenture.com/ProvidentConnector_ProvidentReceiver_ProvidentWSPort/SOPResponse" style="document" />
      <wsdl:input>
        <soap:body use="literal" />
      </wsdl:input>
      <wsdl:output>
        <soap:body use="literal" />
      </wsdl:output>
    </wsdl:operation>
</wsdl:binding>
<wsdl:service name="ProvidentConnector_ProvidentReceiver_ProvidentWSPort">
    <documentation xmlns="http://schemas.xmlsoap.org/wsdl/">BizTalk assembly "ProvidentConnector, Version=1.0.0.0,
Culture=neutral, PublicKeyToken=ae7c9e263f196bff" published web service.</documentation>
    <wsdl:port name="ProvidentConnector_ProvidentReceiver_ProvidentWSPortSoap" binding="tns:ProvidentConnector_ProvidentReceiver_ProvidentWSPortSoap">
      <soap:address location="http://localhost/ProvidentConnector/ProvidentWSPort.asmx" />
    </wsdl:port>
</wsdl:service>
</wsdl:definitions>

wsdd

</service>
</deployment>

-----Original Message-----
From: Patrick Quinn [mailto:[EMAIL PROTECTED]
Sent: 12 July 2005 09:51
To: [email protected]
Subject: BizTalk mulitpart Error when communicating with an Axis service

Hi

The following error is seen from a BizTalk client when it accesses my Axis service.

" Provident Connector Send: Exception invoking WS... The XLANG/s message has no part at index '0'. The total number of parts found in the message is '0'. If you expect a multipart message, check that the pipeline supports multipart messages such as MIME. "

My service is doc/lit wrapped style, taking four strings as arguments in the service call (one of which is an XML document).

A result code of 0:3 (in String format) is returned to the calling method by way of acknowledgement. This all seems to work functionally as expected, despite this error message showing on the client side.

All I want to know really is whether it is likelier that there is a problem with the service, or more likely it is an issue with the client call.

Thanks in advance.

Patrick

=00This e-mail and any attachments may be confidential and/or legally privileged. If you have received this e-mail and you are not a named addressee, please inform Evolving Systems TIS at [EMAIL PROTECTED] and then delete the e-mail from your system. If you are not a named addressee you must not use, disclose, distribute, copy, print or rely on this e-mail. To ensure regulatory compliance and for the protection of our clients and business, Evolving Systems may monitor and read e-mails sent to and from its servers. Although Evolving Systems routinely screens for viruses, addressees should scan this e-mail and any attachments for viruses. Evolving Systems makes no representation or warranty as to the absence of viruses in this e-mail or any attachments.

Registered Office: One Angel Square, Torrents Street, London. EC1V 1PL. Registered number 2325854

=00This e-mail and any attachments may be confidential and/or legally privileged. If you have received this e-mail and you are not a named addressee, please inform Evolving Systems TIS at [EMAIL PROTECTED] and then delete the e-mail from your system. If you are not a named addressee you must not use, disclose, distribute, copy, print or rely on this e-mail. To ensure regulatory compliance and for the protection of our clients and business, Evolving Systems may monitor and read e-mails sent to and from its servers. Although Evolving Systems routinely screens for viruses, addressees should scan this e-mail and any attachments for viruses. Evolving Systems makes no representation or warranty as to the absence of viruses in this e-mail or any attachments.

Registered Office: One Angel Square, Torrents Street, London. EC1V 1PL. Registered number 2325854

RE: BizTalk mulitpart Error when communicating with an Axis service

Reply via email to