Sergey Beryozkin-5 wrote:
>
>
> I suspect it's because Foo schema is actually setting an
> elementFormQualified attribute to true.
> So, even though we bypassed an initial JAXB error, the actual Foo
> children in the incoming sequence are still expected to be qualified
> but this time JAXB just ignores them.
> So, instead of configuring TransformFeature's inTransformElements with
>
> "Foo" : "{http://somevalue}Foo";
>
> try
>
> "*" : "{http://somevalue}*";
>
> which reads as "qualify all the incoming elements with
> http://somevalue namespace"
>
>
Ah yes, I should have experimented the fields within the Class as well as
the Class itself.
I was able to reach success when I specified the actual field names,
i.e......
"fooId": "{http://somevalue}fooId";
I am not able to the the "*" wildcard to work. I'm continuing to try a few
different variations to see if I can get that to work.
FYI, I am not on version 2.4.0 yet, so I am not using the Transform feature.
I am still using inTransformElements on the provider. Not sure if that
makes a difference for being able to use wildcards or not.
Thanks again for your help. I now have a much better understanding of
what's going on.
--
View this message in context:
http://cxf.547215.n5.nabble.com/XMLRootElement-for-parameters-in-REST-method-signatures-tp4537057p4554208.html
Sent from the cxf-user mailing list archive at Nabble.com.
