[
https://issues.apache.org/jira/browse/MYFACES-1737?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_12533456
]
Bernhard Huemer commented on MYFACES-1737:
------------------------------------------
This bug seems to be a duplicate of
https://issues.apache.org/jira/browse/MYFACES-1735, which has been fixed
recently.
> myfaces-impl jar does not include faces-config dtds and thus won't work if
> offline
> ----------------------------------------------------------------------------------
>
> Key: MYFACES-1737
> URL: https://issues.apache.org/jira/browse/MYFACES-1737
> Project: MyFaces Core
> Issue Type: Bug
> Components: General
> Affects Versions: 1.2.0
> Environment: MyFaces 1.2 reading faces-config.xml with a doctype of
> JSF 1.0 or 1.1
> Reporter: Karol Bucek
> Priority: Minor
>
> While initializing faces configuration and being offline (or behind a proxy),
> MyFaces won't start and ends with something like:
> DefaultFacesInitializer.initFaces(126) | Error initializing MyFaces:
> java.net.ConnectException: Connection timed out: connect
> The issue is caused by the parser trying to get the dtd for:
> http://java.sun.com/dtd/web-facesconfig_1_x.dtd when for some reason it
> cannot connect to the http url.
> The dtd is not being resolved from the jar as it is missing in 1.2.0,
> org.apache.myfaces.config.impl.FacesConfigEntityResolver will attempt to
> resolve the resource from org/apache/myfaces/resource, but version 1.2.0 of
> the myfaces-impl.jar is missing the 'older' dtds (it only contains
> org/apache/myfaces/resource/web-facesconfig_1_2.xsd).
> By copying the web-facesconfig_1_0.dtd and the web-facesconfig_1_1.dtd into
> the jar everything works as expected.
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
