cxf-users mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Daniel Kulp <dk...@apache.org>
Subject Re: return element funkiness with 2.3.1
Date Wed, 08 Dec 2010 20:33:01 GMT
On Wednesday 08 December 2010 11:58:07 am Yiannis Mavroukakis wrote:
> Sorry, stupidly forgot to include more info about my setup. I am seeing
> this on the deployed service, I use a code first approach, so it was
> simply a case of updating the version on my pom, recompiling and firing up
> the service. If you need anything specific to debug this I'd be happy to
> help.

I have NO idea what would cause this.  Can  you do something like:

mvn clean dependency:copy-dependencies 
or even just
mvn dependency:tree

with each of the two and see if different versions of things are popping up?

This isn't in OSGi, is it?


Dan



> 
> Thanks,
> 
> Yiannis
> 
> On 8 December 2010 16:53, Daniel Kulp <dkulp@apache.org> wrote:
> > On Wednesday 08 December 2010 11:45:15 am Yiannis Mavroukakis wrote:
> > > Hello everyone,
> > > 
> > > I updated from 2.3.0 to 2.3.1 today, and I noticed that the <return>
> > > element has changed to <_return> any particular reason for this?
> > 
> > No idea really.   Is there any way to create a small test case?
> > 
> > The only thing that really was done around this is with the wsdl2java
> > tool and
> > java2ws tools (is that where you are seeing this), we did a better job of
> > endorsing the jaxws/jaxb 2.2 stuff.   If this is just a runtime thing,
> > then that really wouldn't apply though.
> > 
> > 
> > --
> > Daniel Kulp
> > dkulp@apache.org
> > http://dankulp.com/blog

-- 
Daniel Kulp
dkulp@apache.org
http://dankulp.com/blog

Mime
View raw message