Incidentally for anyone suffering from the same issue, I managed to pull
together a temporary workaround.
I wrote my own version of Spring OXM's FragmentStreamReader, this
effectively cuts the stream into a series of complete fragments. I had the
advantage here of being able to cut out a lot of the very flexible Spring
code that allows you to use different combinations of source and
marshallers. It also allowed me use Woodstox XMLStreamReader directly
instead of needing the Spring adapter to wrap an XMLEventReader (which
seemed to be the source of the problem).
Woodstox have very nicely been a bit more lenient in their implementation of
the XMLStreamReader so test both:
boolean hasURI = (nsURI != null) && (nsURI.length() > 0);
Then it was a matter of writing a custom Spring Batch Item Reader to utilise
the Fragment Reader.
Although its not a very comprehensive solution I am happy to share with
anyone if a permanent solution is not found.
--
View this message in context:
http://www.nabble.com/Mismatch-between-JiBX-and-QName-represntation-of-an-attribute-with-no-namespace--tp23349737p23357928.html
Sent from the jibx-users mailing list archive at Nabble.com.
------------------------------------------------------------------------------
Register Now & Save for Velocity, the Web Performance & Operations
Conference from O'Reilly Media. Velocity features a full day of
expert-led, hands-on workshops and two days of sessions from industry
leaders in dedicated Performance & Operations tracks. Use code vel09scf
and Save an extra 15% before 5/3. http://p.sf.net/sfu/velocityconf
_______________________________________________
jibx-users mailing list
[email protected]
https://lists.sourceforge.net/lists/listinfo/jibx-users
