To change the definition of the xsi and xsd prefixes, you would need to change the source and re-build soap.jar.
The definition of these two prefixes only appears to matter, though, because of some hard-coding in the bean serializer (which causes "xsi:type" to be generated). I will look into fixing this situation. Scott Nichol ----- Original Message ----- From: "Brent Cerrato" <[EMAIL PROTECTED]> To: <[EMAIL PROTECTED]> Sent: Tuesday, November 26, 2002 14:13 Subject: RE: Using old xsi/xsd schemas in 2.3.1 I just attempted that and the result looks as follows (after my writing)... not exactly what I wanted to happen... and when I send this to the test server it tells me it can't find proper deserializers.... is there any way to make the Envelope's xsi/xsd's the 1999 version (and to make the content use null instead of nil)? Thanks!! ~brent <SOAP-ENV:Envelope xmlns:SOAP-ENV="http://schemas.xmlsoap.org/soap/envelope/"; xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance"; xmlns:xsd="http://www.w3.org/2001/XMLSchema";> <SOAP-ENV:Body> <ns1:formFreeSendLookup xmlns:ns1="urn:AgentConnect" SOAP-ENV:encodingStyle="http://schemas.xmlsoap.org/soap/encoding/";> <formFreeSendLookupRequest xsi:type="ns1:FormFreeSendLookupRequest"> <apiVersion xmlns:ns2="http://www.w3.org/1999/XMLSchema-instance"; xmlns:ns3="http://www.w3.org/1999/XMLSchema"; ns2:type="ns3:string">220</apiVersion> <clientSoftwareVersion xmlns:ns4="http://www.w3.org/1999/XMLSchema-instance"; xmlns:ns5="http://www.w3.org/1999/XMLSchema"; ns4:type="ns5:string">100</clientSoftwareVersion> <confirmationNumber xmlns:ns6="http://www.w3.org/1999/XMLSchema-instance"; xmlns:ns7="http://www.w3.org/1999/XMLSchema"; ns6:type="ns7:string">1113585</confirmationNumber> <sendCurrency xmlns:ns8="http://www.w3.org/1999/XMLSchema-instance"; xmlns:ns9="http://www.w3.org/1999/XMLSchema"; ns8:type="ns9:string">USD</sendCurrency> <timeStamp xmlns:ns10="http://www.w3.org/1999/XMLSchema-instance"; xmlns:ns11="http://www.w3.org/1999/XMLSchema"; ns10:type="ns11:timeInstant">2002-11-26T19:09:20.842Z</timeStamp> <token xmlns:ns12="http://www.w3.org/1999/XMLSchema-instance"; xmlns:ns13="http://www.w3.org/1999/XMLSchema"; ns12:type="ns13:long">1038326859886</token> <unitProfileID xmlns:ns14="http://www.w3.org/1999/XMLSchema-instance"; xmlns:ns15="http://www.w3.org/1999/XMLSchema"; ns14:type="ns15:int">1700</unitProfileID> </formFreeSendLookupRequest> </ns1:formFreeSendLookup> </SOAP-ENV:Body> </SOAP-ENV:Envelope> -----Original Message----- From: Scott Nichol [mailto:[EMAIL PROTECTED]] Sent: Tuesday, November 26, 2002 2:07 PM To: [EMAIL PROTECTED] Subject: Re: Using old xsi/xsd schemas in 2.3.1 You create your SOAPMapping registry using a non-default constructor, e.g. SOAPMappingRegistry smr = new SOAPMappingRegistry(null, Constants.NS_URI_1999_SCHEMA_XSD); Scott Nichol ----- Original Message ----- From: "Brent Cerrato" <[EMAIL PROTECTED]> To: <[EMAIL PROTECTED]> Sent: Tuesday, November 26, 2002 12:34 Subject: Using old xsi/xsd schemas in 2.3.1 How do I get apache to use an older schema (like the 1999 schema) when sending a soap request (in version 2.3.1 of the SOAP classes)? I need the functionality provided by the new classes, but the server I am talking to most likely doesn't support the 2001 schema. Will there be any repercussions to this change? Will serializing/deserializing break? Thanks! ~brent cerrato~ Software Engineer - US Mosaic Software, Inc. Tel (office): +1 954 426 1190 x 268 Fax: +1 954 426 1644 http://www.mosaicsoftware.com <http://www.mosaicsoftware.com/> -- To unsubscribe, e-mail: <mailto:[EMAIL PROTECTED]> For additional commands, e-mail: <mailto:[EMAIL PROTECTED]> -- To unsubscribe, e-mail: <mailto:[EMAIL PROTECTED]> For additional commands, e-mail: <mailto:[EMAIL PROTECTED]> -- To unsubscribe, e-mail: <mailto:[EMAIL PROTECTED]> For additional commands, e-mail: <mailto:[EMAIL PROTECTED]>
