Details
-
Type: Bug
-
Status: Closed
-
Priority: Major
-
Resolution: Fixed
-
Affects Version/s: 1.5
-
Component/s: Documentation
-
Labels:None
-
Environment:Operating System: Windows XP
Platform: PC
-
Affects:Documentation (User Guide, Ref. Guide, etc.)
Description
from a submitted comment:
ICEFACES.ORG CONTACT US EMAIL FROM: Will Hoover
ICEfaces.org Username: whoover
Email Address: whoover@nemours.org
-----------------------------------------------------------------------
Just an FYI...
Your ICEfaces_GettingStarted.pdf document contains some incorrect information on
page 21 for the web.xml setup:
<context-param>
<param-name>javax.faces.application.CONFIG_FILES</param-name>
<param-name>/WEB_INF/faces-config.xml</param-name>
</context-param>
According to MyFaces having this entry in our deployment descriptor will force
JSF to load the configuration twice. As a result, this will cause all the phase
listeners to be registered/executed twice.
Reference:
http://wiki.apache.org/myfaces/FAQ#Twice
Jira:
http://issues.apache.org/jira/browse/MYFACES-1338
ICEFACES.ORG CONTACT US EMAIL FROM: Will Hoover
ICEfaces.org Username: whoover
Email Address: whoover@nemours.org
-----------------------------------------------------------------------
Just an FYI...
Your ICEfaces_GettingStarted.pdf document contains some incorrect information on
page 21 for the web.xml setup:
<context-param>
<param-name>javax.faces.application.CONFIG_FILES</param-name>
<param-name>/WEB_INF/faces-config.xml</param-name>
</context-param>
According to MyFaces having this entry in our deployment descriptor will force
JSF to load the configuration twice. As a result, this will cause all the phase
listeners to be registered/executed twice.
Reference:
http://wiki.apache.org/myfaces/FAQ#Twice
Jira:
http://issues.apache.org/jira/browse/MYFACES-1338
Issue Links
- depends on
-
ICE-1646 Remove the redundant "javax.faces.application.CONFIG_FILES" parameter from sample application web.xml files
- Closed
ICEfaces sample applications do not make use of this parameter, so it could easily cause the problem described. I recommend we remove it from the Getting Started guide.