I was just doing some Google'ing, and I was wondering if I could define the soap:body with use="literal" and then define the Element item as a type? And if so, how would I go about defining the types for my method?
-- David B. Bitton [EMAIL PROTECTED] www.codenoevil.com Code Made Fresh DailyT ----- Original Message ----- From: "Simon Fell" <[EMAIL PROTECTED]> To: <[EMAIL PROTECTED]> Sent: Saturday, April 27, 2002 8:22 PM Subject: Re: Represent method in WSDL On Sat, 27 Apr 2002 20:05:07 -0400, in soap you wrote: >My class method requires different encoding styles for each param. The >signature is: > >public String Render(org.w3c.dom.Element source, String xsl_url) > >I use an MSSOAP 2.2 client, building the envelope using the low-level API, >and this poses no problem at all. Since I use the low-level API, a WSDL is >not required. I'd like to publish this though, and therefore I have to >create a WSDL. > >The problem lies with the fact that 'source' requires an encoding type of >"http://xml.apache.org/xml-soap/literalxml";, and 'xsl_url' uses the default >"http://schemas.xmlsoap.org/soap/encoding/";. If I mark the encodingStyle >for soap:body ".../literalxml", will clients (Java and MS) mark all params >within the request envelope as being literalxml, and if so, will Apache SOAP >assume that my method sig is: > >public String Render(org.w3c.dom.Element source, org.w3c.dom.Element >xsl_url) > >How do I get around this dilemma? You can't WSDL only supports a single encoding style for the body and each header, its not possible to indicate that different parts of the body require different encodings. Cheers Simon
