ICEfaces
  1. ICEfaces
  2. ICE-11506

FacesMessage(s) have been enqueued, but may not have been displayed

    Details

    • Type: Bug Bug
    • Status: Open
    • Priority: Major Major
    • Resolution: Unresolved
    • Affects Version/s: EE-3.3.0.GA_P07
    • Fix Version/s: None
    • Component/s: ICE-Components
    • Labels:
      None
    • Environment:
      Production

      Description

      Hi Team,

      We are using ICEFaces 3.x_P07 version with ICE Components and We are facing below Warning Message and The message also showed in the UI but still below warning appeared in Log file.

      INFO: WARNING: FacesMessage(s) have been enqueued, but may not have been displayed.
      sourceId=contactTabForm:mobilecontact[severity=(ERROR 2), summary=(ERROR: Invalid Phone Number.), detail=(ERROR: Invalid Phone Number.)]

        Activity

        Hide
        Mohamed Rawoof Peer Mohamed added a comment - - edited

        This WARNING message is valid because of coding issue and It could be a following reason

        1. Duplicate body or h:body tag available in the same view.
        2. Two times the validation message triggered via java code in the same request (FacesContext.getCurrentInstance().addMessage(clientId, new FacesMessage(FacesMessage.SEVERITY_ERROR, msg, msg)); )

        (Workaround for #2 is change the tag to messages instead of message so that it will accumulate all the messages. Exact Fix is correct your code -> Do not validate two times for the same id in the same call)

        Thanks

        Show
        Mohamed Rawoof Peer Mohamed added a comment - - edited This WARNING message is valid because of coding issue and It could be a following reason 1. Duplicate body or h:body tag available in the same view. 2. Two times the validation message triggered via java code in the same request (FacesContext.getCurrentInstance().addMessage(clientId, new FacesMessage(FacesMessage.SEVERITY_ERROR, msg, msg)); ) (Workaround for #2 is change the tag to messages instead of message so that it will accumulate all the messages. Exact Fix is correct your code -> Do not validate two times for the same id in the same call) Thanks

          People

          • Assignee:
            Unassigned
            Reporter:
            Mohamed Rawoof Peer Mohamed
          • Votes:
            0 Vote for this issue
            Watchers:
            1 Start watching this issue

            Dates

            • Created:
              Updated: