Forgot to mention that in earlier CXF versions one can get the same transformation done by explicitly configuring JSON or JAXB providers:
http://cxf.apache.org/docs/jax-rs-data-bindings.html#JAX-RSDataBindings-CustomizingJAXBXMLandJSONinputandoutput Sergey On Fri, Jul 1, 2011 at 10:51 AM, Sergey Beryozkin <[email protected]> wrote: > Hi, > > On Thu, Jun 30, 2011 at 11:35 PM, dponos <[email protected]> wrote: >> Thank you Stephen, your information definitely helps. I am able to work >> around the issue this way. >> > Starting with CXF 2.4.0 one can solve this issue by configuring > TransformFeature [1] on the server side (and/or client side if > needed), example, when using Spring: > > <bean id="transformFeature" > class="org.apache.cxf.feature.StaxTransfromFeature"> > <property name="inTransformElements"> > <map> > <entry key="Foo" value="{http://acme.com/model}Foo"/> > </map> > </property> > </bean> > > and then link to it: > <jaxrs:server> > <jaxrs:features> > <ref bean="transformFeature"/> > </jaxrs:features> > </jaxrs:server> > > This feature instance will qualify a chosen element in the coming XML > stream coming from default JSONProvider, before this specific element > is consumed by JAXB > > Hope it helps > Sergey > > > [1] > http://cxf.apache.org/docs/transformationfeature.html#TransformationFeature-JAXRS > > >> >> >> -- >> View this message in context: >> http://cxf.547215.n5.nabble.com/XMLRootElement-for-parameters-in-REST-method-signatures-tp4537057p4540370.html >> Sent from the cxf-user mailing list archive at Nabble.com. >> > > > > -- > Sergey Beryozkin > > Application Integration Division of Talend > http://sberyozkin.blogspot.com >
