1

I followed the example here: Why does <h:inputText required="true"> allow blank spaces? to create a "Global" converter to trim all input fields. However, the converter is not being invoked when input fields are submitted. 

@FacesConverter(forClass=String.class) 
... 
<p:inputText value="#{controller.inputValue}"/>

but when I change to:

@FacesConverter("StringTrimmer") 
... 
<p:inputText value="#{controller.inputValue}" converter="StringTrimmer"/>

it works.

Using Mojarra 2.1.7 and PrimeFaces 3.2

Community
  • 1
  • 1
BestPractices
  • 12,738
  • 29
  • 96
  • 140

3 Answers3

3

A converter with a forClass will only be invoked whenever the type of the property is an instance of the specified class. In your particular case, that can only mean that the #{controller.inputValue} is not of type String.

BalusC
  • 1,082,665
  • 372
  • 3,610
  • 3,555
  • i tried it directly with #{inputValue} instead of #{controller.inputValue}, with 'inputvalue' declared as a managedbean within the request scope. it didn't work. should it been always declared as property of a wrapper bean like #{controller.inputValue} ? – arthur May 30 '12 at 15:05
1

If you checked that the bound variable is of type String and the converter still doesn't get called, you may also check the following:

  • If the input component is encapsulated inside a composite component, you may have this issue. In that case, converters would not be called correctly, resulting in your custom method to be never reached. Calling the converter explicitly on the input component solves this.

  • If you add both value="someName" and forClass="someClass" to the @FacesConverter annotation, the forClass attribute will be ignored. This has been reported here.

Community
  • 1
  • 1
Louise
  • 1,451
  • 1
  • 18
  • 40
0

This didnt work because the inputValue was not actually of type String. Once changed to type String-- it worked.

BestPractices
  • 12,738
  • 29
  • 96
  • 140