As usual, these are simply zipped projects, so just unzip and mvn clean install.
(Maven will download everything itself). You'll see the code/mappings
generated/annotated and the roundtrip tested against the sample XML file.
Now about the Hibernate annotations.
It appears that EJB3 spec has some severe flaws which limit its usage with JAXB.
What's relevant to us is:
* There is no way to map a collection of primitive values (List<String>, for
instance). JAXB does generate such fields.
* There are no custom types. You just can't map stuff like QName or
XMLGregorianCalendar - used by JAXB for xsd:QName or xsd:dateTime types.
* There is no accessor infrastructure. This imposes two problems for JAXB. (1)
JAXB geneerates no setters for collections so custom list accessors come quite
handy here. (2) Custom accessors allow to distinguish null/zero/empty semantics
for numeric primitive types using isSet/unset methods.
It seems that Hyperjaxb3 will have several EJB3-vendor specific dialects so I've
started with Hibernate dialect since it's what I'm most familiar with. yes, I
can imagine a "pure" vendor-independent EJB3 solution - but with massing code
augmentation.