abdera-user mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From James M Snell <jasn...@gmail.com>
Subject Re: Controlling serialization w/extensions
Date Wed, 28 Feb 2007 15:30:23 GMT
Without a concrete test case, it would be difficult for me to say with
certainty that it is the stax impl.  However, there is a huge amount of
inconsistency between stax implementations right now due largely to
massive holes in the Stax specification. It would not surprise me in the
least if this was a Stax impl bug.

- James

Adam Constabaris wrote:
> James M Snell wrote:
> <snip>
>>> This symptom suggests that there's a bug in the serializer somewhere
>>> ("I've already output a declaration for those, so I don't need to do it
>>> again"), but the successful unit tests don't fit with that diagnosis.
>> Which Stax parser are you using, btw?
> Don't know why I didn't think of looking there; server was using StAX
> from JDK 1.6.0 and the unit tests were using Woodstox.  I since verified
> trying both parsers w/AXIOM offline, and the StAX implementation appears
> to be the key difference.
> I've filed this with AXIOM
> (https://issues.apache.org/jira/browse/WSCOMMONS-175) (it may or may not
> be "their fault" -- I don't have time to dig into the StAX
> implementations -- but they may want to implement a fix).  Either way, I
> suppose the issue is relevant for anybody deploying Abdera w/1.6.0  --
> watch your StAX implementation, or make sure to add all your
> declarations to the root element.
> cheers,
> AC

View raw message