It is a little bit different context, I guess. With hyperjaxb they are going from XML to object to DB, instead of the other way around, but similar principle as this could be used to go the other direction as well.
-----Original Message----- From: Jason Chaffee [mailto:[email protected]] Sent: Tuesday, April 20, 2010 12:57 PM To: [email protected] Subject: RE: Clarification on using JAX-RS with CXF If you take the position of some at java.net, then it would be that they do belong together. See hyperjaxb3. https://hyperjaxb3.dev.java.net/ -----Original Message----- From: Sergey Beryozkin [mailto:[email protected]] Sent: Tuesday, April 20, 2010 12:51 PM To: [email protected] Subject: Re: Clarification on using JAX-RS with CXF I really not sure what to recommend. On Tue, Apr 20, 2010 at 7:26 PM, Dan King <[email protected]> wrote: > I'm unclear about the following and I'd appreciate help in gaining > clarification. > > 1. Can/should entities that are marked with JPA > annotations also be marked with JAXB annotations for use as > request/response objects? For example is the following acceptable? > > @XmlRootElement(name="Category") > @Entity > @Table(name="category") > public class Category { ... } > > as far as marshaling Category as a JAXB bean, it does not matter what other annotations Category might have > 2. > When using HTTP centric clients, must the client have a copy of the > request/response objects. If yes, is there anyway around it? > Can you clarify please. What problem you seeing, when using WebClients cheers, Sergey > > Thanks. > > -Dan > > > > >
