How to display my application s errors in JSF

Question

In my JSF Facelets app  here s a simplified version of part of my form    lt h form id  myform  gt     lt h inputSecret value    createNewPassword newPassword1   id  newPassword1    gt     lt h message class  error  for  newPassword1    gt     lt h inputSecret value    createNewPassword newPassword2   id  newPassword2    gt     lt h message class  error  for  newPassword2    gt     lt h commandButton value  Continue  action    createNewPassword continueButton     gt   lt  h form gt    I d like to be able to assign an error to a specific h message tag based on something happening in the continueButton   method  Different errors need to be displayed for newPassword and newPassword2  A validator won t really work  because the method that will deliver results  from the DB  is run in the continueButton   method  and is too expensive to run twice    I can t use the h messages tag because the page has multiple places that I need to display different error messages  When I tried this  the page displayed duplicates of every message   I tried this as a best guess  but no luck   public Navigation continueButton             expensiveMethod      if            FacesContext getCurrentInstance   addMessage  newPassword   new FacesMessage  Error  Your password is NOT strong enough              What am I missing  Any help would be appreciated

User · Accepted Answer

In case anyone was curious  I was able to figure this out based on all of your responses combined   This is in the Facelet    lt h form id  myform  gt     lt h inputSecret value    createNewPassword newPassword1   id  newPassword1    gt     lt h message class  error  for  newPassword1  id  newPassword1Error    gt     lt h inputSecret value    createNewPassword newPassword2   id  newPassword2    gt     lt h message class  error  for  newPassword2  id  newPassword2Error    gt     lt h commandButton value  Continue  action    createNewPassword continueButton     gt   lt  h form gt    This is in the continueButton   method   FacesContext getCurrentInstance   addMessage  myForm newPassword1   new FacesMessage PASSWORDS DONT MATCH  PASSWORDS DONT MATCH      And it works  Thanks for the help

User · Answer

FacesContext addMessage String  FacesMessage  requires the component s clientId  not it s id  If you re wondering why  think about having a control as a child of a dataTable  stamping out different values with the same control for each row - it would be possible to have a different message printed for each row  The id is always the same  the clientId is unique per row   So  myform mybutton  is the correct value  but hard-coding this is ill-advised  A lookup would create less coupling between the view and the business logic and would be an approach that works in more restrictive environments like portlets    lt f view gt     lt h form gt       lt h commandButton id  mybutton  value  click        binding    showMessageAction mybutton         action    showMessageAction validatePassword     gt       lt h message for  mybutton    gt     lt  h form gt   lt  f view gt    Managed bean logic       Must be request scope for binding    public class ShowMessageAction        private UIComponent mybutton       private boolean isOK   false       public String validatePassword             if  isOK                return  ok                     else                  invalid             FacesMessage message   new FacesMessage  Invalid password length                FacesContext context   FacesContext getCurrentInstance                context addMessage mybutton getClientId context   message                     return null             public void setMybutton UIComponent mybutton            this mybutton   mybutton             public UIComponent getMybutton             return mybutton

User · Answer

FacesContext addMessage String  FacesMessage  requires the component s clientId  not it s id  If you re wondering why  think about having a control as a child of a dataTable  stamping out different values with the same control for each row - it would be possible to have a different message printed for each row  The id is always the same  the clientId is unique per row   So  myform mybutton  is the correct value  but hard-coding this is ill-advised  A lookup would create less coupling between the view and the business logic and would be an approach that works in more restrictive environments like portlets    lt f view gt     lt h form gt       lt h commandButton id  mybutton  value  click        binding    showMessageAction mybutton         action    showMessageAction validatePassword     gt       lt h message for  mybutton    gt     lt  h form gt   lt  f view gt    Managed bean logic       Must be request scope for binding    public class ShowMessageAction        private UIComponent mybutton       private boolean isOK   false       public String validatePassword             if  isOK                return  ok                     else                  invalid             FacesMessage message   new FacesMessage  Invalid password length                FacesContext context   FacesContext getCurrentInstance                context addMessage mybutton getClientId context   message                     return null             public void setMybutton UIComponent mybutton            this mybutton   mybutton             public UIComponent getMybutton             return mybutton

User · Answer

Remember that   FacesContext context   FacesContext getCurrentInstance    context addMessage  null  new FacesMessage   The message to display in client                    is also valid  because when null is specified as first parameter  it is applied to the whole form   More info  coreservlets com   Outdated

User · Answer

JSF is a beast  I may be missing something  but I used to solve similar problems by saving the desired message to a property of the bean  and then displaying the property via an outputText    lt h outputText     value    CreateNewPasswordBean errorMessage       render    CreateNewPasswordBean errorMessage    null     gt

User · Answer

You also have to include the FormID in your call to addMessage      FacesContext getCurrentInstance   addMessage  myform newPassword1   new FacesMessage  Error  Your password is NOT strong enough        This should do the trick   Regards

User · Answer

Found this while Googling  The second post makes a point about the different phases of JSF  which might be causing your error message to become lost   Also  try null in place of  newPassword  because you do not have any object with the id newPassword

User · Answer

Remember that   FacesContext context   FacesContext getCurrentInstance    context addMessage  null  new FacesMessage   The message to display in client                    is also valid  because when null is specified as first parameter  it is applied to the whole form   More info  coreservlets com   Outdated

User · Answer

You also have to include the FormID in your call to addMessage      FacesContext getCurrentInstance   addMessage  myform newPassword1   new FacesMessage  Error  Your password is NOT strong enough        This should do the trick   Regards

User · Answer

JSF is a beast  I may be missing something  but I used to solve similar problems by saving the desired message to a property of the bean  and then displaying the property via an outputText    lt h outputText     value    CreateNewPasswordBean errorMessage       render    CreateNewPasswordBean errorMessage    null     gt

User · Answer

I tried this as a best guess  but no luck    It looks right to me  Have you tried setting a message severity explicitly  Also I believe the ID needs to be the same as that of a component  i e   you d need to use newPassword1 or newPassword2  if those are your IDs  and not newPassword as you had in the example    FacesContext getCurrentInstance   addMessage  newPassword1                        new FacesMessage FacesMessage SEVERITY ERROR   Error Message       Then use  lt h message for  newPassword1    gt  to display the error message on the JSF page

User · Answer

Found this while Googling  The second post makes a point about the different phases of JSF  which might be causing your error message to become lost   Also  try null in place of  newPassword  because you do not have any object with the id newPassword

User · Answer

FacesContext addMessage String  FacesMessage  requires the component s clientId  not it s id  If you re wondering why  think about having a control as a child of a dataTable  stamping out different values with the same control for each row - it would be possible to have a different message printed for each row  The id is always the same  the clientId is unique per row   So  myform mybutton  is the correct value  but hard-coding this is ill-advised  A lookup would create less coupling between the view and the business logic and would be an approach that works in more restrictive environments like portlets    lt f view gt     lt h form gt       lt h commandButton id  mybutton  value  click        binding    showMessageAction mybutton         action    showMessageAction validatePassword     gt       lt h message for  mybutton    gt     lt  h form gt   lt  f view gt    Managed bean logic       Must be request scope for binding    public class ShowMessageAction        private UIComponent mybutton       private boolean isOK   false       public String validatePassword             if  isOK                return  ok                     else                  invalid             FacesMessage message   new FacesMessage  Invalid password length                FacesContext context   FacesContext getCurrentInstance                context addMessage mybutton getClientId context   message                     return null             public void setMybutton UIComponent mybutton            this mybutton   mybutton             public UIComponent getMybutton             return mybutton

User · Answer

JSF is a beast  I may be missing something  but I used to solve similar problems by saving the desired message to a property of the bean  and then displaying the property via an outputText    lt h outputText     value    CreateNewPasswordBean errorMessage       render    CreateNewPasswordBean errorMessage    null     gt

User · Answer

Found this while Googling  The second post makes a point about the different phases of JSF  which might be causing your error message to become lost   Also  try null in place of  newPassword  because you do not have any object with the id newPassword

User · Answer

You also have to include the FormID in your call to addMessage      FacesContext getCurrentInstance   addMessage  myform newPassword1   new FacesMessage  Error  Your password is NOT strong enough        This should do the trick   Regards

User · Answer

I tried this as a best guess  but no luck    It looks right to me  Have you tried setting a message severity explicitly  Also I believe the ID needs to be the same as that of a component  i e   you d need to use newPassword1 or newPassword2  if those are your IDs  and not newPassword as you had in the example    FacesContext getCurrentInstance   addMessage  newPassword1                        new FacesMessage FacesMessage SEVERITY ERROR   Error Message       Then use  lt h message for  newPassword1    gt  to display the error message on the JSF page

User · Answer

Simple answer  if you don t need to bind it to a specific component      Java               FacesMessage message   new FacesMessage FacesMessage SEVERITY ERROR   Authentication failed   null               FacesContext context   FacesContext getCurrentInstance                context addMessage null  message           XHTML                lt h messages gt  lt  h messages gt

User · Answer

Found this while Googling  The second post makes a point about the different phases of JSF  which might be causing your error message to become lost   Also  try null in place of  newPassword  because you do not have any object with the id newPassword

User · Answer

You also have to include the FormID in your call to addMessage      FacesContext getCurrentInstance   addMessage  myform newPassword1   new FacesMessage  Error  Your password is NOT strong enough        This should do the trick   Regards

User · Answer

JSF is a beast  I may be missing something  but I used to solve similar problems by saving the desired message to a property of the bean  and then displaying the property via an outputText    lt h outputText     value    CreateNewPasswordBean errorMessage       render    CreateNewPasswordBean errorMessage    null     gt

User · Answer

I tried this as a best guess  but no luck    It looks right to me  Have you tried setting a message severity explicitly  Also I believe the ID needs to be the same as that of a component  i e   you d need to use newPassword1 or newPassword2  if those are your IDs  and not newPassword as you had in the example    FacesContext getCurrentInstance   addMessage  newPassword1                        new FacesMessage FacesMessage SEVERITY ERROR   Error Message       Then use  lt h message for  newPassword1    gt  to display the error message on the JSF page

User · Answer

Simple answer  if you don t need to bind it to a specific component      Java               FacesMessage message   new FacesMessage FacesMessage SEVERITY ERROR   Authentication failed   null               FacesContext context   FacesContext getCurrentInstance                context addMessage null  message           XHTML                lt h messages gt  lt  h messages gt

User · Answer

FacesContext addMessage String  FacesMessage  requires the component s clientId  not it s id  If you re wondering why  think about having a control as a child of a dataTable  stamping out different values with the same control for each row - it would be possible to have a different message printed for each row  The id is always the same  the clientId is unique per row   So  myform mybutton  is the correct value  but hard-coding this is ill-advised  A lookup would create less coupling between the view and the business logic and would be an approach that works in more restrictive environments like portlets    lt f view gt     lt h form gt       lt h commandButton id  mybutton  value  click        binding    showMessageAction mybutton         action    showMessageAction validatePassword     gt       lt h message for  mybutton    gt     lt  h form gt   lt  f view gt    Managed bean logic       Must be request scope for binding    public class ShowMessageAction        private UIComponent mybutton       private boolean isOK   false       public String validatePassword             if  isOK                return  ok                     else                  invalid             FacesMessage message   new FacesMessage  Invalid password length                FacesContext context   FacesContext getCurrentInstance                context addMessage mybutton getClientId context   message                     return null             public void setMybutton UIComponent mybutton            this mybutton   mybutton             public UIComponent getMybutton             return mybutton

User · Answer

I tried this as a best guess  but no luck    It looks right to me  Have you tried setting a message severity explicitly  Also I believe the ID needs to be the same as that of a component  i e   you d need to use newPassword1 or newPassword2  if those are your IDs  and not newPassword as you had in the example    FacesContext getCurrentInstance   addMessage  newPassword1                        new FacesMessage FacesMessage SEVERITY ERROR   Error Message       Then use  lt h message for  newPassword1    gt  to display the error message on the JSF page

[jsf] How to display my application's errors in JSF?

Examples related to jsf

Examples related to error-handling

Examples related to facelets