[hibernate-dev] did hibernate.org crash?
Carlo de Wolf
cdewolf at redhat.com
Tue Feb 3 15:19:07 EST 2015
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 at redhat.com
>>> <mailto:smarlow at 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 at redhat.com <mailto:smarlow at redhat.com>
>>> <mailto:smarlow at redhat.com <mailto:smarlow at 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 at lists.jboss.org
>> https://lists.jboss.org/mailman/listinfo/hibernate-dev
>>
> _______________________________________________
> hibernate-dev mailing list
> hibernate-dev at lists.jboss.org
> https://lists.jboss.org/mailman/listinfo/hibernate-dev
>
>
More information about the hibernate-dev
mailing list