Interesting. If I disable schema (xml) validation, it works. Seems that
Envers is just not producing valid XML.
On Thu, Mar 12, 2015 at 8:35 PM, Steve Ebersole <steve(a)hibernate.org> wrote:
OK, so I ran into a speed bump with Envers. For those not familiar,
Envers essentially iterates over all the entity mappings Hibernate has
built for user entities and dynamically builds a DOM(4J) Document
representing the audit entity corollaries. I had planned to simply bridge
that to our JAXB process in ORM using a DOMSource to wrap the Document
Envers built as input into the StAX+JAXB pipeline. Well it turns out that
does not really work. It did not work with the JDK built in parsers. I
even tried swapping in Woodstox but ran into problems there too.
So, unless someone has a quick suggestion for this, I will have to convert
Envers to build the JAXB model directly. Which will take some time.
On Wed, Mar 11, 2015 at 10:45 AM, Steve Ebersole <steve(a)hibernate.org>
> You mean y'all? ;)
> On Wed, Mar 11, 2015 at 9:39 AM, Gunnar Morling <gunnar(a)hibernate.org>
>> 2015-03-11 10:20 GMT+01:00 Hardy Ferentschik <hardy(a)hibernate.org>:
>>> On Wed, Mar 11, 2015 at 09:43:49AM +0100, Emmanuel Bernard wrote:
>>> > Woohoo
>>> "1,291 changed files with 34,601 additions and 220 deletions" - not
>> My thoughts are with the poor soul who had to review that PR ;)
>>> hibernate-dev mailing list