I am NOT in Red Hat VPN/Network and I do confirm the site is up.
2015-02-04 10:15 GMT+01:00 Emmanuel Bernard <emmanuel(a)hibernate.org>:
For info hibernate.org
seems to be
“down” *if* you are behind the Red Hat VPN (I can still access though). So that’s probably
some IT filtering going on because we are some kind of subversive site. That makes sense
Anyways, fixing the dtd resolution to go local only remains important.
> On 03 Feb 2015, at 20:44, Scott Marlow <smarlow(a)redhat.com> wrote:
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:firstname.lastname@example.org>> wrote:
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
>>> whole call
>>> 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
>>> <smarlow(a)redhat.com <mailto:email@example.com>
>>> On 11/19/2014 11:26 AM, Steve Ebersole wrote:
>>> ORM has had local resolution of these DTDs forever.
>>> is amiss
>>> in your set up. I just ran ORM tests and the DTDs are
>>> 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 mailing list
hibernate-dev mailing list