The purpose of this blog post is to help a user we were assisting on Twitter who wanted to use JAXB to marshal JPA entities into XML but only wanted a portion of the entities to be used. By default JAXB will traverse all available relationships including lazy ones that have not been loaded to build a complete XML document for the provided entities.
Here is a simple example reading a Customer with an Address (1:1) and PhoneNumber(s) (1:M) from a database and marshalling it into XML using EclipseLink JPA with EclipseLink MOXy.
Setup code for JPA and JAXB:
// JPAExample: Find & Marshall Customer
EntityManagerFactory emf =
EntityManager em = emf.createEntityManager();
JAXBContext jaxbContext = JAXBContext.newInstance(Customer.class);
Customer customer = em.find(Customer.class, 1);When executed this generates the following XML and causes the customer's address and phone numbers to be loaded from the database.
Now, if we wanted to generate a partial XML document including only the Customer's basic attributes and its address's attributes we could use a copy group to create a partial copy and marshal it:
Customer customer = em.find(Customer.class, (long) 1);Now the generated XML appears as:
CopyGroup cg = new CopyGroup();
JpaEntityManger nativeEM = em.unwrap(JpaEntityManager.class);
Customer custCopy = (Customer) nativeEM .copy(customer, cg);
marshaller.marshal(custCopy , System.out);
There are other combined uses of AttributeGroup that can be used to control what is fetched and loaded as well but this copy example should illustrate some of the options available and how EclipseLink JPA and MOXy components can be easily used together.
Additional MOXy examples available here.