Weird JSF "h:messages" tag behavior

[Cold Gin]

Hi. I am displaying error messages via the <h:messages> tag, but this strange prefix shows up with the message:

j_id_jsp_1488097600_1:formField3: Validation Error: Value is less than allowable minimum of '5'

How can I suppress the j_id_jsp_1488097600_1:formField3: prefix, and what causes it to be displayed? Do I have something specified incorrectly? The tag in my JSP looks like this:

 
<h:inputText id="formField3" value="#{maintForm.formField3}">
<f:validateLength minimum="5"/>
</h:inputText>
 

Thanks.

[Bob Good]

I think the key for the message is in a FacesMessageBundle.properties file with this value:

javax.faces.validator.LengthValidator.MINIMUM Value is less than allowable minimum of '{0}'

you faces config may have this in it:

<application>
<message-bundle>FacesMessageBundle</message-bundle>
</application>

The file name could be anything, this is just an example.

[Cold Gin]

Thanks for replying, Bob. I have the following in faces.config to reference my custom messages:

    
 
 <application>
  <resource-bundle>
   <base-name>mypackagename.application</base-name>
   <var>msgs</var>
  </resource-bundle>
 </application>
 

And then I have the application.properties file which resides in that package. The messages are being picked up correctly, I just don't understand why I am getting the extra verbage on the message...

Thanks.

[Bob Good]

Try and add a new faces message bundle to play with the predefined messages. Here are the ones I use:

    
javax.faces.component.UIInput.CONVERSION Invalid entry, not the correct data type
javax.faces.component.UIInput.REQUIRED Value is required 
javax.faces.component.UISelectOne.INVALID Value is not a valid option 
javax.faces.component.UISelectMany.INVALID Value(s) are not a valid selection 
javax.faces.validator.NOT_IN_RANGE Specified attribute is not between the expected values of {0} and {1} 
javax.faces.validator.DoubleRangeValidator.MAXIMUM Value is greater than allowable maximum of '{0}' 
javax.faces.validator.DoubleRangeValidator.MINIMUM Value is less than allowable minimum of '{0}' 
javax.faces.validator.DoubleRangeValidator.TYPE Value is not of the correct type 
javax.faces.validator.LengthValidator.MAXIMUM Value is greater than allowable maximum of '{0}' 
javax.faces.validator.LengthValidator.MINIMUM Value is less than allowable minimum of '{0}' 
javax.faces.validator.LongRangeValidator.MAXIMUM Value is greater than allowable maximum of '{0}' 
javax.faces.validator.LongRangeValidator.MINIMUM Value is less than allowable minimum of '{0}' 
javax.faces.validator.LongRangeValidator.TYPE Value is not of the correct type 

[ March 07, 2008: Message edited by: Bob Good ]

[Mark Spritzler]

"Cold Gin",
Welcome to the JavaRanch.

We're a friendly group, but we do require members to have valid display names.

Display names must be two words: your first name, a space, then your last name. Fictitious names are not allowed.

Please edit your profile and correct your display name since accounts with invalid display names get deleted.

[Cold Gin]

Hmmm. I tried adding all of your messages to my message bundle, but I got the same result... I also tried this, which got rid of the prefix, but now the replacement variable '{0}' does not get replaced with the minimum size inside of the message string. I also tried using '{1}' inside the message string:

    
 
<h:inputText id="formField3" value="#{maintForm.formField3}" validatorMessage="#{msgs.invalidTextLength}">
<f:validateLength minimum="5"/>
</h:inputText>
 

Message file looks like:

   
 
javax.faces.component.UIInput.CONVERSION Invalid entry, not the correct data type
javax.faces.component.UIInput.REQUIRED Value is required 
javax.faces.component.UISelectOne.INVALID Value is not a valid option 
javax.faces.component.UISelectMany.INVALID Value(s) are not a valid selection 
javax.faces.validator.NOT_IN_RANGE Specified attribute is not between the expected values of {0} and {1} 
javax.faces.validator.DoubleRangeValidator.MAXIMUM Value is greater than allowable maximum of '{0}' 
javax.faces.validator.DoubleRangeValidator.MINIMUM Value is less than allowable minimum of '{0}' 
javax.faces.validator.DoubleRangeValidator.TYPE Value is not of the correct type 
javax.faces.validator.LengthValidator.MAXIMUM Value is greater than allowable maximum of '{0}' 
javax.faces.validator.LengthValidator.MINIMUM Value is less than allowable minimum of '{0}' 
javax.faces.validator.LongRangeValidator.MAXIMUM Value is greater than allowable maximum of '{0}' 
javax.faces.validator.LongRangeValidator.MINIMUM Value is less than allowable minimum of '{0}' 
javax.faces.validator.LongRangeValidator.TYPE Value is not of the correct type 
invalidTextLength Value is less than allowable minimum of '{0}'
formField1Label Form Field 1:
formField2Label Form Field 2:
formField3Label Form Field 3:
formField4Label Form Field 4:
 

Thanks.

[Bob Good]

your bundle is different than this bundle:

<application>
<message-bundle>FacesMessageBundle</message-bundle>
</application>

create a separate properties file for the java message bundle, and add to faces config like this. Works for me, and the message are overridden properly, and I can change the ones I do not like.
[ March 07, 2008: Message edited by: Bob Good ]

[Cold Gin]

Bob - Thank you very much. Before reading your last post, I realized that the weird prefix seems to be caused by having my variable markers enclosed by single quotes '{0}' instead of double quotes i.e.) "{0}". The second thing is that I needed to have the message-bundle entry in the faces config also (just as you were saying). So my faces.config now looks like:

    
 
 <application>
  <message-bundle>mypackagename.application</message-bundle>
 </application>
 
  <application>
  <resource-bundle>
   <base-name>mypackagename.application</base-name>
   <var>msgs</var>
  </resource-bundle>
 </application>
 

And finally, the messages:

    
 
javax.faces.component.UIInput.CONVERSION=Invalid entry, not the correct data type
javax.faces.component.UIInput.REQUIRED=Value is required 
javax.faces.component.UISelectOne.INVALID=Value is not a valid option 
javax.faces.component.UISelectMany.INVALID=Value(s) are not a valid selection 
javax.faces.validator.NOT_IN_RANGE=Specified attribute is not between the expected values of "{0}" and "{1}" 
javax.faces.validator.DoubleRangeValidator.MAXIMUM=Value is greater than allowable maximum of "{0}"
javax.faces.validator.DoubleRangeValidator.MINIMUM=Value is less than allowable minimum of "{0}" 
javax.faces.validator.DoubleRangeValidator.TYPE=Value is not of the correct type 
javax.faces.validator.LengthValidator.MAXIMUM=Value is greater than allowable maximum of "{0}" 
javax.faces.validator.LengthValidator.MINIMUM=Value is less than allowable minimum of "{0}"
javax.faces.validator.LongRangeValidator.MAXIMUM=Value is greater than allowable maximum of "{0}" 
javax.faces.validator.LongRangeValidator.MINIMUM=Value is less than allowable minimum of "{0}" 
javax.faces.validator.LongRangeValidator.TYPE=Value is not of the correct type
formField1Label=Form Field 1:
formField2Label=Form Field 2:
formField3Label=Form Field 3:
formField4Label=Form Field 4:
 

[Ben Souther]

"Cold Gin",
Please check your private messages.
-Ben

[Mark Spritzler]

Originally posted by Ben Souther:
"Cold Gin",
Please check your private messages.
-Ben

So this is now "Cold Gin"'s second warning in the same thread.

"Cold Gin", if you do not change your display name by tomorrow, I will close your accout.

Mark

[Krishna Srinivasan]

JSf Error Messages Example

[ March 12, 2008: Message edited by: Krishna Srinivasan ]
[ March 12, 2008: Message edited by: Krishna Srinivasan ]

[Sunny Wear]

Hi,
You can also try to just add the requiredMessage attribute to any input tag in JSF 1.2, as that allows you to customize your error message.


<h:inputText id="name" required="true" requiredMessage="You must
enter a name" />

[Bauke Scholtz]

Or by specifying a label. If it is present, it will be used instead of the client id.