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

[Eric H (JIRA)]

    [ http://jira.jboss.com/jira/browse/JBSEAM-2441?page=comments#action_12401347 ] 
            
Eric H commented on JBSEAM-2441:
--------------------------------

This came up again while Seam was trying to parse a page.xml file, resulting in the app not working at a customer site which had a firewall, when the app had worked in the office.  See: http://chiralsoftware.com/blog/DTD-declarations-in-XML-files-are-d69ec4c5afaa0922.html .  This situation is probably also causing needless traffic on the JBoss.com servers, just like it is at W3C: http://www.w3.org/blog/systeam/2008/02/08/w3c_s_excessive_dtd_traffic .  Finally, if a server is delaying rendering a page until it does a fetch from jboss.com, that is needlessly impacting the user performance of the application.  I notice that seamframework.org is not the fastest site on the net, and I wonder if it is slow because of DTD re-fetching.

> Deployment fails with unhelpful errors if DTD/xsd can't be found
> ----------------------------------------------------------------
>
>                 Key: JBSEAM-2441
>                 URL: http://jira.jboss.com/jira/browse/JBSEAM-2441
>             Project: JBoss Seam
>          Issue Type: Bug
>          Components: Core
>    Affects Versions: 2.0.0.GA
>         Environment: Linux, Java 6
>            Reporter: Eric H
>             Fix For: 2.1.x
>
>
> 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-b6b5f0cbb79e5cd8.html

-- 
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