Ah, there is a difference in how core and hem are loading these.
is likely a bug, could you open a Jira?
On Wed, Nov 19, 2014 at 12:15 PM, Scott Marlow <smarlow(a)redhat.com
is an initial call stack into
org.hibernate.service.__internal.JaxbProcessor. I'm debugging on
the Hibernate 4.3 branch and don't hit any break points in
org.hibernate.cfg.__Configuration#entityResolver. Perhaps I ended
up in the wrong class, not sure. I also set break points in
org.hibernate.internal.util.__xml.DTDEntityResolver (don't see
The first exception that I see is http://pastebin.com/CYd0aNzE
On 11/19/2014 11:46 AM, Steve Ebersole wrote:
I should have been more complete :)
You can either set a breakpoint or crank up logging on that class.
Breakpoint debugging is probably better as you could see the
stack. These resolvers use a lot of delegation. You could also
at org.hibernate.cfg.__Configuration#entityResolver to verify which
specific resolver is being used.
On Wed, Nov 19, 2014 at 10:35 AM, Scott Marlow
<mailto:email@example.com <mailto:firstname.lastname@example.org>>> wrote:
On 11/19/2014 11:26 AM, Steve Ebersole wrote:
ORM has had local resolution of these DTDs forever.
in your set up. I just ran ORM tests and the DTDs are
Thanks for checking.
Can you make sure control is getting through our registered
EntityResolver? Ultimately, this should be resolved
I'll give this a try.