2:43 p.m.
HHH-9511 shows the call stack (should answer where/why).
On 02/03/2015 03:22 PM, Steve Ebersole wrote:
Great question! Scott?
On Tue, Feb 3, 2015 at 2:19 PM, Carlo de Wolf <cdewolf(a)redhat.com
<mailto:cdewolf@redhat.com>> wrote:
Why and where do we have such a dependency?
Carlo
On 02/03/2015 08:44 PM, Scott Marlow wrote:
Hibernate.org is down (seeing WildFly testsuite failures).
On 11/19/2014 03:33 PM, Scott Marlow wrote:
On 11/19/2014 02:43 PM, Steve Ebersole wrote:
Ah, there is a difference in how core and hem are
loading these. This
is likely a bug, could you open a Jira?
I created HHH-9511 for this.
On Wed, Nov 19, 2014 at 12:15 PM, Scott Marlow
<smarlow(a)redhat.com <mailto:smarlow@redhat.com>
<mailto:smarlow@redhat.com <mailto:smarlow@redhat.com>>>
wrote:
http://pastebin.com/Baz7FRyf 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
org.hibernate.internal.util.______xml.DTDEntityResolver).
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
whole call
stack. These resolvers use a lot of
delegation. You could also
look
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
<smarlow(a)redhat.com
<mailto:smarlow@redhat.com> <mailto:smarlow@redhat.com
<mailto:smarlow@redhat.com>>
<mailto:smarlow@redhat.com
<mailto:smarlow@redhat.com> <mailto:smarlow@redhat.com
<mailto:smarlow@redhat.com>>>> wrote:
On 11/19/2014 11:26 AM, Steve Ebersole
wrote:
ORM has had local resolution of
these DTDs forever.
Something
is amiss
in your set up. I just ran ORM
tests and the DTDs are
being
resolved
locally properly.
Thanks for checking.
Can you make sure control is getting
through our registered
EntityResolver? Ultimately, this
should be resolved
by
org.hibernate.internal.util.______xml.DTDEntityResolver
I'll give this a try.
_________________________________________________
hibernate-dev mailing list
hibernate-dev(a)lists.jboss.org
<mailto:hibernate-dev@lists.jboss.org>
https://lists.jboss.org/__mailman/listinfo/hibernate-dev
<https://lists.jboss.org/mailman/listinfo/hibernate-dev>
_________________________________________________
hibernate-dev mailing list
hibernate-dev(a)lists.jboss.org <mailto:hibernate-dev@lists.jboss.org>
https://lists.jboss.org/__mailman/listinfo/hibernate-dev
<https://lists.jboss.org/mailman/listinfo/hibernate-dev>