Custom message with FacesContext.getCurrentInstance().addMessage is not displayed in page (JSF)

Question

My page:

...
    <div id="header">
       <!-- content header -->
     </div>
     <div id="content">
       <h:messages />
       <h:ouputText value="#{example.text}" />
     </div>
...

My managedBean:

public class ExampleManagedBean(){
       private String text;


       public String getText(){
           FacesContext.getCurrentInstance().
                   addMessage(null, 
                      new FacesMessage(FacesMessage.SEVERITY_WARN, 
                                       "Warning message...", null));
           return text;
       }

       public void setText(String text){
           this.text = text;
       }
   }

My problem is that the warning message not is rendered in page. Why?

Yes, there is an <f:view>. The page not is refreshed, because it is the first page. — bblanco
– bblanco, Commented Mar 2, 2010 at 8:57
@Bozho: Is <f:view> is required for popping out messages for display? — Rachel
– Rachel, Commented Apr 11, 2012 at 18:07
not sure anymore :) it has been 2 years since I last used JSF — Bozho
– Bozho, Commented Apr 11, 2012 at 20:00

lexicore · Accepted Answer · 2010-03-29 12:51:19Z

3

I have two ideas.

First, the message is added in the getText() getter. If h:messages is rendered before h:outputText, then the message might not be there yet when h:messages is rendered.

Second, messages disappear on redirects.

answered Mar 29, 2010 at 12:51

lexicore

43.9k17 gold badges142 silver badges228 bronze badges

Sign up to request clarification or add additional context in comments.

Comments

Piotr Kochański · Accepted Answer · 2010-02-26 21:22:02Z

2

FacesMessage is send to <h:messages/> during validation phase of JSF lifecycle. In your case getter is used to derive bean property value and no validation is going on, so the message is empty.

In theory you can use setter validation, but this is a well known antipattern.

You can do "by hand" validation, but in a different way

 <div id="content">
    <h:messages />
    <h:form>
        <h:outputText value="#{example.text}" />
        <h:commandButton value="Click" action="#{example.action}"/>
    </h:form>
 </div>

and the action method is

public String action(){
   FacesContext.getCurrentInstance().
        addMessage(null,
            new FacesMessage(FacesMessage.SEVERITY_WARN,
                                       "Warning message...", null));
           return null;
}

Much cleaner approach would use built-in or custom validator.

answered Feb 26, 2010 at 21:22

Piotr Kochański

22.9k7 gold badges76 silver badges77 bronze badges

2 Comments

BalusC Over a year ago

Sorry, but you're completely wrong. The by OP posted code is valid and supposed to work. The FacesMessages are derived during renderresponse, regaredless of where they're been set. The problem lies somewhere else, the OP has yet to clarify it based on the comment of Bozho. Until then it's only shooting in the dark.

bblanco Over a year ago

Yes, there is an <f:view>. The page not is refreshed, because it is the first page.

Collectives™ on Stack Overflow

Custom message with FacesContext.getCurrentInstance().addMessage is not displayed in page (JSF)

2 Answers 2

Comments

2 Comments

Your Answer

Hot Network Questions

Collectives™ on Stack Overflow

2 Answers 2

Comments

2 Comments

Your Answer

Sign up or log in

Post as a guest

Related