Found this very interesting - HyperJaxb3...
The typical scenario of usage is: Schema-driven XML-object-relational database persistence using Java.
With hyperjaxb3, once can just persist the data from XML document instances to Relational databases with very minimum and generic ORM coding in Java. In a nutshell, the XJB (XML-Java Binding) file contains the JAXB/ORM configuration and along with XSD file, hyperjaxb creates the respective Java files (during the build time) with necessary JPA annotations for ORM. So, for the programmers, now we already have a bunch of business domain objects that are JPA compliant ready with zero-coding. These can be readily used with some underlying JPA providers, to have an abstract persistence logic defined before hitting the actual RDBMS. More info available here at Hyperjaxb3 Confluence.
The typical scenario of usage is: Schema-driven XML-object-relational database persistence using Java.
With hyperjaxb3, once can just persist the data from XML document instances to Relational databases with very minimum and generic ORM coding in Java. In a nutshell, the XJB (XML-Java Binding) file contains the JAXB/ORM configuration and along with XSD file, hyperjaxb creates the respective Java files (during the build time) with necessary JPA annotations for ORM. So, for the programmers, now we already have a bunch of business domain objects that are JPA compliant ready with zero-coding. These can be readily used with some underlying JPA providers, to have an abstract persistence logic defined before hitting the actual RDBMS. More info available here at Hyperjaxb3 Confluence.
No comments:
Post a Comment