Sergey, The main change between them that MAY affect the XML binding is going from JAXB 2.0.x to JAXB 2.1.x. The generated code from xjc can be quite different and could potentially change things.
I know a bug was fixed in the HTTP binding for 2.2.2 in regards to the root element things. I'm wondering if that may have affected this or not. Dan On Sun June 14 2009 3:47:26 pm Sergey Beryozkin wrote: > Hi, > > As far as I'm aware no significant changes have been made to the HTTP > binding recently, I haven't done any work with it for sure. Perhaps > there've been some cosmetic changes but I'm not aware of them. > > We've agreed to deprecate the HTTP binding as all the focus now is on > enhancing the JAX-RS runtime. > > > The problem is that we need to keep the same XML messages format for > > backward compatibility. > > Can you please post a sample class annotated with HTTPBinding > annotations and XML message which is expected by current clients ? > > Thanks, Sergey > > > -----Original Message----- > From: Gabriel Guardincerri [mailto:[email protected]] > Sent: 12 June 2009 20:08 > To: [email protected] > Subject: How to migrate REST HTTP-binding to JAX-RS and keep the xml > messages format? > > > Hi, > > We have a lot of WS that were implemented using HTTP-binding of CXF > 2.0.11, > but when we tried to migrate CXF to 2.2.2 we found out that HTTP-binding > do > not pass params correctly. So we were trying to migrate those services > to > JAX-RS. The problem is that we need to keep the same XML messages format > for > backward compatibility. We tried with the three data binding providers > that > are in the jaxrs package XMLBeansElementProvider, JAXBElementProvider > and > AegisElementProvider, but none of them have the same XML format for > messages > that HTTP-binding has. > > Is there a way to do so? I mean, to implement services with JAX-RS and > use > the same XML data binding that has HTTP-binding? Or a way to build the > same > XML messages? > > Of course, if there is a way to make HTTP-binding work in version 2.2.2 > or > 2.1.5, it will be the best solution. > > Thanks, > > Gabriel -- Daniel Kulp [email protected] http://www.dankulp.com/blog
