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? -- David B. Bitton [EMAIL PROTECTED] www.codenoevil.com Code Made Fresh DailyT
