hi,

Is there a possibility to control axis to add or prevent the generation of
the nsxx namespace declarations.

I.e.:

<soapenv:Envelope
xmlns:soapenv="http://schemas.xmlsoap.org/soap/envelope/";
xmlns:xsd="http://www.w3.org/2001/XMLSchema";
xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance";>
 <soapenv:Body>
  <requestRouting xmlns="http://some.tld/net";>
   <Request xmlns="">
    <ns1:Header xmlns:ns1="http://some.tld/net";>
     <ns1:RequestID>1016657</ns1:RequestID>
     <ns1:Timestamp>2004-11-11T21:05:58.726Z</ns1:Timestamp>
     <ns1:EnvFlag>2</ns1:EnvFlag>
     <ns1:Version>1.0.0</ns1:Version>
    </ns1:Header>
.
.

or send:

<?xml version="1.0" encoding="UTF-8"?>
<soapenv:Envelope
xmlns:soapenv="http://schemas.xmlsoap.org/soap/envelope/";
xmlns:xsd="http://www.w3.org/2001/XMLSchema";
xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance";>
 <soapenv:Body>
  <requestRouting xmlns="http://some.tld/net";>
   <ReqRouting xmlns="">
    <Header>
     <RequestID>818394866663406592</RequestID>
     <Timestamp>2004-11-20T17:01:14.432Z</Timestamp>
     <EnvFlag>0</EnvFlag>
     <Version>1.0.0</Version>
    </Header>
.

I know these both are basicaly the same but I have to control if axis add
the ns prefix or not. Is there a configuration point to handle this?

I googled around and search FAQ (mailing-list search seems to be down) and
didn't find anything useful for now (at least no solution but several
people asking the same question without success).

kr,
gerhard

Reply via email to