No, this issue is a bit different. This is purely a JAXB runtime issue. In this case, the shema he is using is definitely "qualified" for the eBx type. All the elements are definitely coming out qualified. However, what he would like is for the elements to set/use the default namespace instead of a namespace prefix.
I honestly don't know if that can be done or not. We pretty much just pass the jaxb objects to the jaxb runtime and let it spit out whatever it spits out. I don't know what level of control the runtime provides us to manipulate the prefixes. Log a feature request. Someone that is actually more familiar with the JAXB internals may be able to pick it up. Dan On Wednesday 29 August 2007, Glen Mazza wrote: > Yes, that has come up before: > http://issues.apache.org/jira/browse/CXF-884 > > CXF may have a flag turning off that in the future. Preliminary > analysis of the matter has shown though that the change is not trivial > to do and would cascade through multiple parts of the code. > > Glen > > Am Mittwoch, den 29.08.2007, 09:33 -0700 schrieb sameh: > > I'm using CXF 2.0.1-incubator in weblogic 10 > > My WSDL imports a schema (xsd) which imports another schema (xsd) > > and it all validates with no problems > > > > when I get the response back the namespace alias is on every tag and > > I would like to know if I can have it on the top level tag only > > > > Current response: > > <soap:Envelope > > xmlns:soap="http://schemas.xmlsoap.org/soap/envelope/";><soap:Body><n > >s3:DocResponse mlns:ns2="http://www.synoran.com/ebx/v4/types"; > > xmlns:ns3="http://www.synoran.com/sde/se/types";><payload><ns2:eBx><n > >s2:eBxRq><ns2:SignonRq><ns2:SignonRecCHT><ns2:SignonPswd><ns2:SignonR > >ole>String</ns2:SignonRole></ns2:Signos been listening to us… nPswd></ns2:SignonRecCHT><ns2:C > >lientDt>2001-12-17T09:30:47.0Z</ns2:ClientDt></ns2:SignonRq></ns2:eBx > >Rq></ns2:eBx></payload></ns3:DocResponse></soap:Body></soap:Envelope> > > > > Expected response > > <soap:Envelope > > xmlns:soap="http://schemas.xmlsoap.org/soap/envelope/";><soap:Body><n > >s:DocResponse > > mlns:ns="http://www.synoran.com/sde/se/types";><payload><eBx > > xmlns="http://www.synoran.com/ebx/v4/types";><eBxRq><SignonRq><Signon > >RecCHT><SignonPswd><SignonRole>String</SignonRole></SignonPswd></Sign > >onRecCHT><ClientDt>2001-12-17T09:30:47.0Z</ClientDt></SignonRq></eBxR > >q></eBx></payload></ns:DocResponse></soap:Body></soap:Envelope> > > > > my beans.xml: > > <beans xmlns="http://www.springframework.org/schema/beans"; > > xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance"; > > xmlns:jaxws="http://cxf.apache.org/jaxws"; > > xsi:schemaLocation=" > > http://www.springframework.org/schema/beans > > http://www.springframework.org/schema/beans/spring-beans.xsd > > http://cxf.apache.org/jaxws > > http://cxf.apache.org/schemas/jaxws.xsd";> > > > > <import resource="classpath:META-INF/cxf/cxf.xml" /> > > <import resource="classpath:META-INF/cxf/cxf-extension-soap.xml" > > /> <import resource="classpath:META-INF/cxf/cxf-servlet.xml" /> > > > > <jaxws:endpoint id="SDEService" > > implementor="com.synoran.sde.se.SDEServiceImpl" > > address="/SDEService"> > > > > <jaxws:properties> > > <entry key="javax.xml.stream.XMLInputFactory" > > value="com.ctc.wstx.stax.WstxInputFactory" /> > > <entry key="javax.xml.stream.XMLOutputFactory" > > value="com.ctc.wstx.stax.WstxOutputFactory" /> > > <entry key="javax.xml.stream.XMLEventFactory" > > value="com.ctc.wstx.stax.WstxEventFactory" /> > > </jaxws:properties> > > </jaxws:endpoint> > > > > </beans> > > > > Is there a tag that I'm missing or is that something CXF cannot > > currently accomplish? -- J. Daniel Kulp Principal Engineer IONA P: 781-902-8727 C: 508-380-7194 [EMAIL PROTECTED] http://www.dankulp.com/blog
