cxf-users mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Mark Streit <>
Subject Re: Webservice response mismatch between WAS 6.1 and WAS 8
Date Mon, 11 Jun 2012 18:22:34 GMT
I would think it is likely possible that there is a classloader issue (Dan
alludes to that below in terms of what Stax parser is being picked up) and
here are some things to consider:

1) AFAIK - JAX-WS support *in WAS 6.1 *had to be provided with some sort of
"Feature Pack" add-on installation (uses Axis2)
2) For WAS 8, it now has all the JAX-WS support built-in already in the
same way WAS 7 did and again, it uses Axis2 - there was no "Feature Pack"
mess to deal with in WAS 7.
3) I would assume you had to do things like Glen Mazza's blog discusses to
"get around" the IBM stack where CXF (or Metro for that matter - anything
other than Axis2) would be used:
This talks about getting the CXF stack to be the JAX-WS engine and avoid
all the Axis2 stuff on the server side.
4) Since the issue is being seen on the CLIENT side here, you may want to
check the *classloader setting for the client side application* that is
making the call to the backend service since you want it to see the CXF
distribution BEFORE it picks up the IBM/Axis2 stack components as well.

Hope this helps...

On Mon, Jun 11, 2012 at 2:05 PM, Daniel Kulp <> wrote:

> On Friday, June 08, 2012 02:50:22 PM nhrraj wrote:
> > Thanks Dan for responding.
> >
> > I understand those tags are interchangeable.
> >
> > The issue is with the client deserializing framework which deserializes
> > the first tag into a null element and the second one into a empty
> > string('')
> CXF isn't the client framework, is it?   For CXF clients, both of them
> should be deserialized to an empty string.
> > This happens only when I use aegis databinding with simple frontend
> > configuration.
> >
> > Why is the aegis databinding with simple frontend configuration behaving
> > differently when deployed in was6.1 and was8?
> Likely a different Stax parser being picked up.     Aegis pretty much ends
> up calling:
> writer.writeStartElement(....);
> writer.writeEndElement();
> The parser MAY be doing something to  optimize them down into a single tag.
> Don't really know.
> Dan
> > Please let me know if you have any suggestions.
> >
> > --
> > View this message in context:
> >
> > 6-1-and-WAS-8-tp5709311p5709441.html Sent from the cxf-user mailing list
> > archive at



  • Unnamed multipart/alternative (inline, None, 0 bytes)
View raw message