Details
-
Type:
New Feature
-
Status: Closed
-
Priority:
Major
-
Resolution: Invalid
-
Affects Version/s: 2.0.2
-
Fix Version/s: None
-
Component/s: Framework
-
Labels:None
-
Environment:ICEfaces 2
Description
Right now, because of ICE-6820, it's possible to disable the FacesMessagePhaseListener propagation of faces messages for an application, in the web.xml, using the org.icefaces.messagePersistence context-param:
<context-param>
<param-name>org.icefaces.messagePersistence</param-name>
<param-value>true</param-value>
</context-param>
And it's possible to disable it on a page by page basis, using the icecore:config tag:
<icecore:config messagePersistence="false"/>
And it might be possible to temporarily disable the faces message propagation for limited durations by using a ValueExpression with the icecore:config messagePersistence attribute. But there's no granularity in controlling whether global messages or component messages are not propagated, or messages specific to one single component. For these, we should add APIs to FacesMessagePhaseListener.
<context-param>
<param-name>org.icefaces.messagePersistence</param-name>
<param-value>true</param-value>
</context-param>
And it's possible to disable it on a page by page basis, using the icecore:config tag:
<icecore:config messagePersistence="false"/>
And it might be possible to temporarily disable the faces message propagation for limited durations by using a ValueExpression with the icecore:config messagePersistence attribute. But there's no granularity in controlling whether global messages or component messages are not propagated, or messages specific to one single component. For these, we should add APIs to FacesMessagePhaseListener.
Activity
- All
- Comments
- History
- Activity
- Remote Attachments
- Subversion