Alternative entity representation -
Be careful with the embed-xml option you can easily create circular references that result in an endless loop! Finally, data in an XML representation is transactional and persistent, so you can modify queried XML elements and let Hibernate take care of updating the underlying tables: Element itemXML = (Element) dom4jSession.get(Item.class, storedItemId); itemXML.element(”item-details”) .attribute(”initial-price”) .setValue(”100″); session.flush(); // Hibernate executes UPDATEs Element userXML = (Element) dom4jSession.get(User.class, storedUserId); Element newItem = DocumentHelper.createElement(”item”); Element newItemDetails = newItem.addElement(”item-details”); newItem.addAttribute(”seller-id”, userXml.attribute(”id”).getValue() ); newItemDetails.addAttribute(”initial-price”, “123″); newItemDetails.addAttribute(”description”, “A third item”); dom4jSession.save(Item.class.getName(), newItem); dom4jSession.flush(); // Hibernate executes INSERTs There is no limit to what you can do with the XML that is returned by Hibernate. You can display, export, and transform it in any way you like. See the dom4j documentation for more information. Finally, note that you can use all three built-in entity modes simultaneously, if you like. You can map a static POJO implementation of your domain model, switch to dynamic maps for your generic user interface, and export data into XML. Or, you can write an application that doesn t have any domain classes, only dynamic maps and XML. We have to warn you, though, that prototyping in the software industry often means that customers end up with the prototype that nobody wanted to throw away would you buy a prototype car? We highly recommend that you rely on static domain models if you want to create a maintainable system.
Go visit our java server pages services for a reliable, lowcost webhost to satisfy all your needs.