No, it is not a bug. Your WSDL mixes RPC and Document style.

The WS-I Basic Profile allows only one body part in doc/literal message. If
you want to send individual parameters, you must use RPC/Literal, but
neither Axis nor .NET supports RPC/Literal. 

Instead you should use the "wrapped" programming convention. It simulates
RPC style but generates a doc/literal message.

You need to wrap your two input parameters with a wrapper element. 

Your types section should look something like this:

  <schema elementFormDefault="qualified"
targetNamespace="http://DefaultNamespace";
xmlns="http://www.w3.org/2001/XMLSchema";>
   <element name="signRequest">
     <complexType>
       <sequence>
         <element name="in0" type="xsd:base64Binary"/>
         <element name="in1" type="xsd:base64Binary"/>
       </sequence>
     </complexType>
   </element>
   <element name="signRequestReturn" type="xsd:base64Binary"/>
  </schema>
 </wsdl:types>

And your input message should look like this:

   <wsdl:message name="signRequestRequest">
      <wsdl:part element="impl:signRequest" name="parameters"/>
   </wsdl:message>

You must also remove the parameterOrder attribute from your wsdl:operation.

Anne

-----Original Message-----
From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] 
Sent: Thursday, July 22, 2004 8:20 AM
To: [EMAIL PROTECTED]
Subject: PLEASE HELP ME!!! - WS-I Basic Profile compatibility



Hi axis' users, 
I'm using axis 1.2 beta. I have tryed to generate the stub clients for a web
service using the Wireless Toolkit 2.1. The deployed WSDL is:


*******************************************************
<?xml version="1.0" encoding="UTF-8"?>
<wsdl:definitions targetNamespace="http://DefaultNamespace";
xmlns:apachesoap="http://xml.apache.org/xml-soap";
xmlns:impl="http://DefaultNamespace"; xmlns:intf="http://DefaultNamespace";
xmlns:wsdl="http://schemas.xmlsoap.org/wsdl/";
xmlns:wsdlsoap="http://schemas.xmlsoap.org/wsdl/soap/";
xmlns:xsd="http://www.w3.org/2001/XMLSchema";>
<!--WSDL created by Apache Axis version: 1.2beta
Built on Mar 31, 2004 (12:47:03 EST)-->
 <wsdl:types>
  <schema elementFormDefault="qualified"
targetNamespace="http://DefaultNamespace";
xmlns="http://www.w3.org/2001/XMLSchema";>
   <element name="in0" type="xsd:base64Binary"/>
   <element name="in1" type="xsd:base64Binary"/>
   <element name="signRequestReturn" type="xsd:base64Binary"/>
  </schema>
 </wsdl:types>

   <wsdl:message name="signRequestRequest">

      <wsdl:part element="impl:in0" name="in0"/>

      <wsdl:part element="impl:in1" name="in1"/>

   </wsdl:message>

   <wsdl:message name="signRequestResponse">

      <wsdl:part element="impl:signRequestReturn" name="signRequestReturn"/>

   </wsdl:message>

   <wsdl:portType name="caInt">

      <wsdl:operation name="signRequest" parameterOrder="in0 in1">

         <wsdl:input message="impl:signRequestRequest"
name="signRequestRequest"/>

         <wsdl:output message="impl:signRequestResponse"
name="signRequestResponse"/>

      </wsdl:operation>

   </wsdl:portType>

   <wsdl:binding name="caSoapBinding" type="impl:caInt">

      <wsdlsoap:binding style="document"
transport="http://schemas.xmlsoap.org/soap/http"/>

      <wsdl:operation name="signRequest">

         <wsdlsoap:operation soapAction=""/>

         <wsdl:input name="signRequestRequest">

            <wsdlsoap:body use="literal"/>

         </wsdl:input>

         <wsdl:output name="signRequestResponse">

            <wsdlsoap:body use="literal"/>

         </wsdl:output>

      </wsdl:operation>

   </wsdl:binding>

   <wsdl:service name="caIntService">

      <wsdl:port binding="impl:caSoapBinding" name="ca">

         <wsdlsoap:address location="http://localhost/axis/services/ca"/>

      </wsdl:port>

   </wsdl:service>

</wsdl:definitions>


****************************************


The Wireless Toolkit give me the following message:


warning: ignoring operation "signRequest": more than one part in input
message
warning: Port "ca" does not contain any usable operations


I need an help please...It seems to be a bug...is it? 

Luigi Coppolino

----------------------------------------------------------------
This message was sent using IMP, the Internet Messaging Program.

Reply via email to