Hi, sorry for a delay,
I have it working with 3.1.0-SNAPSHOT (should also with 3.0.3).
I did reproduce this error with CXF 2.7.14. A fix must've been quite
sensitive given that it did not make it to CXF 2.7.x.
In general, dealing with explicit collections is problematic IMHO for
JAX-RS services given that the interoperability decreases though might
work in some cases when diff JAX-RS stacks are used on two ends.
The explicit collections of XmlRootElement-annotated beans is supported
in CXF 2.7.x too, but the collections of XmlType only elements is not.
Please try CXF 3.0.3 or, if possible, get the beans wrapping the
collections generated instead - this is done automatically for JAXWS but
not for JAX-RS. You can get JAXB generating such beans by using the
anonymous complex types and possibly other options...
Sergey
On 06/01/15 18:32, criedluv wrote:
Sergey Beryozkin wrote
Can you provide a test case please ?
Unmarshalling a payload into an explicit collection is tested in CXF
JAX-RS system tests but I need to have a test available to investigate
further.
Can you also try CXF 2.7.14 ? The issue may have been fixed there
Cheers, Sergey
Sergey, I attached a CXF JAXRS/WS client and endpoint. The client first
calls the method using WS in question and successfully returns. It then
calls the same method using RS. Within the invoked, called method, the list
in question arrives with objects indicating _the_ unmarshalling issue.
This is very likely a config issue on my part.
I went to 2.17.14 which the example includes. but doesn't seem to fix the
issue.
See my readme along with sample app test case. Let me know if you need
anything.
thank you.
examples.zip <http://cxf.547215.n5.nabble.com/file/n5752828/examples.zip>
--
View this message in context:
http://cxf.547215.n5.nabble.com/java-lang-ClassCastException-com-sun-org-apache-xerces-internal-dom-ElementNSImpl-cannot-be-cast-to-X-tp5752756p5752828.html
Sent from the cxf-user mailing list archive at Nabble.com.
