1

This :

<h:outputLabel for="birthdate">Birthdate (yyyy-MM-dd)</h:outputLabel>
<h:inputText id="birthdate" value="#{userController.user.birthdate}">
    <f:convertDateTime pattern="yyyy-MM-dd" />
    <f:ajax event="blur" render="birthdateMessage" />
</h:inputText>
<h:message id="birthdateMessage" for="birthdate" />

works like a charm in the form. But I can't seem to find a way to move this validation at the entity:

@Temporal(TemporalType.DATE) // pattern ?
@Past
private Date birthdate;

If I remove the <f:convertDateTime pattern="yyyy-MM-dd" /> the form won't validate correctly. So should I keep this in the form - or is there a way to pass the validation in the entity (as I've done with the rest of the fields like email etc)

Bonus: is this the correct way of passing a Date to the persistent layer ? Does it take care of timezones etc ? I always use Joda in SE and IIRC Date is one of the most problematic Java classes. But when I reverse engineered the entities from the tables (using the Eclipse JPA project option Create Entities from tables) that's what I got (in the (MySQL) table the birthdate attribute is of type DATE).

EDIT: I find it better style to have the all validations at the entity than at the view or at the controller - any objections welcome

BalusC
  • 1,082,665
  • 372
  • 3,610
  • 3,555
Mr_and_Mrs_D
  • 32,208
  • 39
  • 178
  • 361

1 Answers1

1

The <f:convertDateTime> isn't a validator, but a converter. The JSR303 Bean Validation API doesn't offer converters, only validators. That's why it can't be supplanted by some JSR303 annotation.

As to time zone, JSF relies by default on GMT. If you make sure the rest of your environment is also relying on GMT, then you're safe. If you however rely on a different time zone, then you can tell JSF that on either an application-wide basis or on a converter-specific basis. Detail can be found in this answer: JSF convertDateTime renders the previous day.

Community
  • 1
  • 1
BalusC
  • 1,082,665
  • 372
  • 3,610
  • 3,555
  • I guess it makes sense to have the converter on the View level - as it is about how I want the date entered - :shrug: :) – Mr_and_Mrs_D Feb 04 '14 at 09:39
  • 1
    Yup. Without a converter it would be impossible to set the property in the model. Those model annotations can only work on already-set properties. – BalusC Feb 04 '14 at 09:42