There are many cases that avoid using Hibernate Tools from being usable when some remote resources are not available, specifically when tooling cannot access remote schema. Tooling should not be blocked by such a things and should allow offline mode. Error below demonstrates blocked Hibernate console during sourceforge is down.
org.hibernate.HibernateException: Could not parse configuration: /home/jpeterka/workspace/tmp/b2/mvn-hibernate43-ent/src/main/java/hibernate.cfg.xml Could not parse configuration: /home/jpeterka/workspace/tmp/b2/mvn-hibernate43-ent/src/main/java/hibernate.cfg.xml org.dom4j.DocumentException: Server returned HTTP response code: 503 for URL: http://hibernate.sourceforge.net/hibernate-configuration-3.0.dtd Nested exception: Server returned HTTP response code: 503 for URL: http://hibernate.sourceforge.net/hibernate-configuration-3.0.dtd Server returned HTTP response code: 503 for URL: http://hibernate.sourceforge.net/hibernate-configuration-3.0.dtd Nested exception: Server returned HTTP response code: 503 for URL: http://hibernate.sourceforge.net/hibernate-configuration-3.0.dtd org.dom4j.DocumentException: Server returned HTTP response code: 503 for URL: http://hibernate.sourceforge.net/hibernate-configuration-3.0.dtd Nested exception: Server returned HTTP response code: 503 for URL: http://hibernate.sourceforge.net/hibernate-configuration-3.0.dtd Server returned HTTP response code: 503 for URL: http://hibernate.sourceforge.net/hibernate-configuration-3.0.dtd Nested exception: Server returned HTTP response code: 503 for URL: http://hibernate.sourceforge.net/hibernate-configuration-3.0.dtd
- is related to
-
JBIDE-20340 Hibernate console cannot be expanded because of inaccessible dtd
- Closed