RE: Request Message type information has multiple parts (!) / WSD L he lp

[Weston, Toby]

Thanks Anne, you're a star!

---

From: Anne Thomas Manes [mailto:[EMAIL PROTECTED]
Sent: 28 November 2005 14:12
To: axis-user@ws.apache.org
Subject: Re: Request Message type information has multiple parts (!) / WSDL he lp

Document/literal exchanges documents, not parameters. Therefore your message should contain at most one body part.

Create another element which is a complex type that is a sequence of your two parameter elements:

<element name="generateRequest">
  <complexType>
    <sequence>
      <element name="param1" type="xsd:string" />
      <element name="properties" type="apachesoap:Map" />
    </sequence>
   </complexType>
 </element>

And change your message def to:

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

Anne

Also, make sure that you've defined the apachesoap:Map type.

On 11/28/05, Weston, Toby <[EMAIL PROTECTED] > wrote:

Folks,

Anyone see anything like this;

"Request Message type information has multiple parts than one single wrapped
complexType. Use WRAPPED/LITERAL if interoping with some other soap stack
becomes a problem"

I suspect the parameters to my document/literal service as I have something
like this;

<wsdl:message name="generateRequest">
        <wsdl:part name="param1" element="impl:param1" />
        <wsdl:part name="properties" element="impl:properties" />
</wsdl:message>

The schema looks like;

<element name="param1" type="xsd:string" />
<element name="properties" type="apachesoap:Map" />

I'm terrible at WSDL so if this is incorrect, could someone point out the
correct syntax pls?

I'm getting null pointer exceptions, that the properties (the HashMap) come
through to the server as null each time and I can't figure out why!

Cheers,
Toby