Hi Sergey,
thanks for the fast patch.
I will try it on Thursday as I have not the right environment here
currently.
Also, JAXBElementProvider has a problem regarding lists of primitive
types, like a list of strings, but I will report in more detail on
Thursday, too.
Another major issue:
As we make extensively use of XmlJavaTypeAdapter, we realized that it is
good supported in the data classes used for parameters / return values
of web methods, but the support is not good when directly annotating
parameters/return value of web methods with XmlJavaTypeAdapter itself:
* for non-RESTful services, we solved the problem by using JAXB v2.2.2
(maybe also earlier versions would work, but actually not that version
delivered with CXF).
* for RESTful services, XmlJavaTypeAdapter works as expected when
applied for parameters, with following exceptions:
**@PathParam refers to the BoundType, and not to the ValueType (so it
e.g. tries to find a static valueOf() method in the BoundType); this
actually makes no sense, and I think this bug is caused since the
processing of PathParam normally not considers JAXB annotations, since
JAXB is only one possible data binding for REST.
**Also lists do not work, as XmlJava TypeAdapter should be applied to
the list items and not to the list object itself (there is no problem
with non-RESTful services in this regard)
So for the two exceptions, we had to use the ValueType directly in our
REST methods, and (un)marshal them with the XmlAdapter "by hand".
Is it possible to contribute some very useful code for testing of
RESTful services (which should be also useful for non-testing purposes)?
Saying this, I could provide test cases using this code, showing all of
the above problems.
