cxf-users mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Benson Margulies" <bim2...@basistech.com>
Subject RE: Aegis and JAXB-WS
Date Wed, 05 Sep 2007 22:48:02 GMT
I'll do it, and I promise to run the tests :-)

> -----Original Message-----
> From: Daniel Kulp [mailto:dkulp@apache.org]
> Sent: Wednesday, September 05, 2007 5:51 PM
> To: cxf-user@incubator.apache.org
> Subject: Re: Aegis and JAXB-WS
> 
> 
> This actually wouldn't be hard to do if someone wants to pick it up.
> There are only three places that we create XmlSchema objects:
> 
> 1) AegisDatabinding.java - around line 268 add a
> e.addNamespaceDeclaration(...) call
> 
> 2) ReflectionServiceFactoryBean - in getOrCreateSchema add a tns to
the
> nsMap.
> 
> 3) JAXBSchemaInitializer - in createBridgeXsElement and
> buildExceptionType, add tns to the nsMap.
> 
> There are probably a BUNCH of unit tests that would then also need to
be
> updated.   Tests that do xpath asserts will need to be adjusted,
etc....
> 
> Dan
> 
> 
> On Wednesday 05 September 2007, Glen Mazza wrote:
> > OK, I would agree then, "tns" is indeed more readable than "ns1" for
> > the target namespace.
> >
> > Glen
> >
> > Am Mittwoch, den 05.09.2007, 13:18 -0400 schrieb Benson Margulies:
> > > I'm changing the subject, sorry. I happened to notice yesterday
that
> > > when it *is* CXF that generates, it lets targetNamespace items
fall
> > > into ns1.
> > >
> 
> 
> 
> 
> --
> J. Daniel Kulp
> Principal Engineer
> IONA
> P: 781-902-8727    C: 508-380-7194
> daniel.kulp@iona.com
> http://www.dankulp.com/blog

Mime
View raw message