The onlky way that I can think of to make it happen is to manually add xsi: and xsd: namespace declarations to the env:body that override the xsi: and xsd: namespace declarations in the env:envelope.
A better suggestion is to convince the service provider to upgrade his service to support the XML Schema standard. (XML Schema 1999 was a Working Draft -- not a standard)
Anne
At 09:54 AM 8/27/2003 +0100, you wrote:
(Reposting as have had no responses and am stuck !)
> Hi, > > I am connecting to a SOAP server which expects : > <SOAP-ENV:Envelope > xmlns:SOAP-ENC="http://schemas.xmlsoap.org/soap/encoding/"; > SOAP-ENV:encodingStyle="http://schemas.xmlsoap.org/soap/encoding/"; > xmlns:SOAP-ENV="http://schemas.xmlsoap.org/soap/envelope/"; > xmlns:xsi="http://www.w3.org/1999/XMLSchema-instance"; > xmlns:xsd="http://www.w3.org/1999/XMLSchema";> > > i.e. XMLSchema 1999 not 2001 > > I am using Axis to generate a request - it is generated with > 2001/XMLSchema. > Can I get Axis to generate a SOAP request using XMLSchema 1999 ? > > I saw a number of posts related to this dated the end of last year but > none since. > I have tried some of the options outlined > (messageContext.setSchemaVersion() etc. but all to no avail...) > At the time it didn't seem to be possible to do this (without tinkering > with the Axis source code yourself). > Is this still the case ? > If not, how do I configure Axis to generate using XMLSchema 1999 ? > > Any suggestions welcome... > > (I am using Axis 1.1) > > Thanks in advance, > Irial
> Irial Conroy > Software Engineer > Am-Beo Ltd. > +353 91 730 814 Direct > +353 91 730 737 Office > +353 91 751 002 Fax www.am-beo.com > ------------------------------ > This message may contain proprietary and valuable information of > Am-Beo. Am-Beo asserts its copyright to any proprietary information that > may have been supplied and the proscription of third party disclosure of > any such proprietary information. > >
