We're using Aegis databinding, and the front end client is javascript
using http://www.guru4.net/articoli/javascript-soap-client/en/
And the binding XML in my beans.xml is...
<bean id="aegisBean"
class="org.apache.cxf.aegis.databinding.AegisDatabinding"/>
<bean id='jaxws-and-aegis-service-factory'
class="org.apache.cxf.jaxws.support.JaxWsServiceFactoryBean">
<property name="dataBinding" ref="aegisBean"/>
<property name="serviceConfigurations">
<list>
<bean
class="org.apache.cxf.jaxws.support.JaxWsServiceConfiguration"/>
<bean
class="org.apache.cxf.aegis.databinding.AegisServiceConfiguration"/>
<bean
class="org.apache.cxf.service.factory.DefaultServiceConfiguration"/>
</list>
</property>
</bean>
-----Original Message-----
From: Benson Margulies [mailto:[EMAIL PROTECTED]
Sent: Thursday, November 08, 2007 2:17 PM
To: [email protected]
Subject: RE: SOAP Namspace change in 2.0.3 - Please Advise
What front end and data binding.
> -----Original Message-----
> From: Vespa, Anthony J [mailto:[EMAIL PROTECTED]
> Sent: Thursday, November 08, 2007 1:07 PM
> To: [email protected]
> Subject: SOAP Namspace change in 2.0.3 - Please Advise
>
> Hello,
>
> Playing with the RC for 2.0.3 has fixed some of my issues, but I have
a
> new one that has arisen.
>
> The responses come back something like...
>
> <soap:Envelope xmlns:soap="http://schemas.xmlsoap.org/soap/envelope/";>
> <soap:Body>
> <ns1:getMessageThreadResponse
> xmlns:ns1="http://soap.ws.test.com/";>
> <ns1:getMessageThreadResult>
> <ns1:responseArray>
> <ns2:anyType ns3:type="ns1:wsMessage"
> xmlns:ns2="http://cxf.apache.org/arrays";
> xmlns:ns3="http://www.w3.org/2001/XMLSchema-instance";>
>
> ...
>
> Is there any way to prevent having ns1 / ns2 prefixed to each level as
> the name? This is causing some issue with our front end client code
and
> client library (in Ajax) - I'm not sure if this is part of other
> discussions that are on-going. Ideally I'd just like the document to
> drop the NS prefixes.
>
> Thanks!
>
> -Tony
