[jbossseam-issues] [JBoss JIRA] Updated: (JBSEAM-2441) Deployment fails with unhelpful errors if DTD can't be found

[ http://jira.jboss.com/jira/browse/JBSEAM-2441?page=all ] Eric H updated JBSEAM-2441: --------------------------- Description: If there is an incorrect DTD URL in files parsed by dom4j, dom4j attempts to fetch the DTD over the net. This is inherently bad because unknown, non-secure resources (DTD files) are being silently added to the application classpath. What is worse, if the file is not found it fails with an unhelpful error, which is dependent on the specific network problem. For example, if name resolution does work, but routing does not work, the application fails (after a delay) with a no route to host error and no indication of which file failed. Really, the XML parser should never attempt to get a resource over the net, unless it has been explicitly configured to do so. See: http://chiralsoftware.com/blog/No-route-to-host-while-parsing-b6b5f0cbb79... was: If there is an incorrect DTD URL in files parsed by dom4j, dom4j attempts to fetch the DTD over the net. This is inherently bad because unknown, non-secure resources (DTD files) are being silently added to the application classpath. What is worse, if the file is not found it fails with an unhelpful error, which is dependent on the specific network problem. For example, if name resolution does work, but routing does not work, the application fails (after a delay) with a no route to host error and no indication of which file failed. Really, the XML parser should never attempt to get a resource over the net, unless it has been explicitly configured to do so. See: [url]http://chiralsoftware.com/blog/No-route-to-host-while-parsing-b6b5f0c...] -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://jira.jboss.com/jira/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira