ICEfaces
  1. ICEfaces
  2. ICE-7137

Add APIs for discontinuing propagation of specific existing faces messages

          Details

          • Type: New Feature New Feature
          • Status: Closed
          • Priority: Major 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.

              Activity

              Ascending order - Click to sort in descending order
              Hide
              Permalink
              Mahmoud Saleh added a comment -

              is this working in version 2.0.2 ? because i tried it and it doesn't work !

              Show
              Mahmoud Saleh added a comment - is this working in version 2.0.2 ? because i tried it and it doesn't work !
              Hide
              Permalink
              Mark Collette added a comment -

              Is what working in ICEfaces 2.0.2? This jira shows a deficiency in 2.0.2 that is not fixed yet, since the jira is still open. The techniques of using the context-param or the icecore:config tag were each added at different points. I'm not sure when the context-param was released, but the icecore:config tag solution will be available in the upcoming ICEfaces release in the next few weeks.

              http://wiki.icefaces.org/display/ICE/Core+Tags#CoreTags-messagePersistence

              Show
              Mark Collette added a comment - Is what working in ICEfaces 2.0.2? This jira shows a deficiency in 2.0.2 that is not fixed yet, since the jira is still open. The techniques of using the context-param or the icecore:config tag were each added at different points. I'm not sure when the context-param was released, but the icecore:config tag solution will be available in the upcoming ICEfaces release in the next few weeks. http://wiki.icefaces.org/display/ICE/Core+Tags#CoreTags-messagePersistence
              Hide
              Permalink
              Mahmoud Saleh added a comment -

              my mistake, misunderstanding, thanks for clarifying, just want to know if this solution is provided in a beta version, and how to get it ? because i am stuck with this problem for so long.

              Show
              Mahmoud Saleh added a comment - my mistake, misunderstanding, thanks for clarifying, just want to know if this solution is provided in a beta version, and how to get it ? because i am stuck with this problem for so long.
              Hide
              Permalink
              Ken Fyten added a comment -

              Marking as Closed / Invalid as part of legacy ICEfaces 1.x, 2.x JIRA cleanup.

              Note: This issue may be resolved in a newer ICEfaces release, available here: http://www.icesoft.org/java/downloads/icefaces-downloads.jsf

              If the issue persists with the current ICEfaces release, please create a new JIRA for it.

              Show
              Ken Fyten added a comment - Marking as Closed / Invalid as part of legacy ICEfaces 1.x, 2.x JIRA cleanup. Note: This issue may be resolved in a newer ICEfaces release, available here: http://www.icesoft.org/java/downloads/icefaces-downloads.jsf If the issue persists with the current ICEfaces release, please create a new JIRA for it.

                People

                • Assignee:
                  Unassigned
                  Reporter:
                  Mark Collette
                • Votes:
                  0 Vote for this issue
                  Watchers:
                  1 Start watching this issue

                  Dates

                  • Created:
                    Updated:
                    Resolved: