ICEfaces
  1. ICEfaces
  2. ICE-1127

Need to implement BridgeFacesContext.getMaximumSeverity()

          Details

          • Type: Bug Bug
          • Status: Closed
          • Priority: Minor Minor
          • Resolution: Fixed
          • Affects Version/s: 1.5.1
          • Fix Version/s: 1.7RC1, 1.7
          • Component/s: Framework
          • Labels:
            None
          • Environment:
            Operating System: Windows XP
            Platform: PC

            Description

            noted in the forum: http://www.icefaces.org/JForum/posts/list/3194.page

            need to implement FacesContext.getMaximumSeverity() for BridgeFacesContext

              Issue Links

              blocks

              Bug - A problem which impairs or prevents the functions of the product. ICE-2478 Problems running on Sun RI JSF1.2_06 - _08 libraries

              • Major - Major loss of function.
              • Closed
              is duplicated by

              Bug - A problem which impairs or prevents the functions of the product. ICE-2790 BridgeFacesContext#maximumSeverity is not implemented

              • Major - Major loss of function.
              • Closed

                Activity

                Ascending order - Click to sort in descending order
                Hide
                Permalink
                Greg Dick added a comment -

                I have implemented this method. Ted, maybe you can check this, I'm not sure exactly when (or if) to reset the maximum severity.

                The JSF source states that the method is to:

                Return the maximum severity level recorded on any

                • {@link javax.faces.application.FacesMessage}

                  s that has been queued, whether or not they are

                • associated with any specific {@link UIComponent}

                  . If no such messages

                • have been queued, return <code>null</code>.</p>

                Currently, I'm resetting the maximum severity to null when the messages are retrieved. Thusly, the maximumSeverity will represent the maximum severity of any messages enqueued since the last time all the messages were retrieved.

                Show
                Greg Dick added a comment - I have implemented this method. Ted, maybe you can check this, I'm not sure exactly when (or if) to reset the maximum severity. The JSF source states that the method is to: Return the maximum severity level recorded on any {@link javax.faces.application.FacesMessage} s that has been queued, whether or not they are associated with any specific {@link UIComponent} . If no such messages have been queued, return <code>null</code>.</p> Currently, I'm resetting the maximum severity to null when the messages are retrieved. Thusly, the maximumSeverity will represent the maximum severity of any messages enqueued since the last time all the messages were retrieved.
                Hide
                Permalink
                Ted Goddard added a comment -

                Looks good, including the reset.

                Show
                Ted Goddard added a comment - Looks good, including the reset.
                Hide
                Permalink
                Adi König added a comment -

                The maxSeverity member never will be reset (1.7RC1)

                Show
                Adi König added a comment - The maxSeverity member never will be reset (1.7RC1)

                  People

                  • Assignee:
                    Unassigned
                    Reporter:
                    Philip Breau
                  • Votes:
                    0 Vote for this issue
                    Watchers:
                    0 Start watching this issue

                    Dates

                    • Created:
                      Updated:
                      Resolved: