Public void initialize(ZipCode zipCode) { } public boolean isValid(String worth , ConstraintValidatorContext context) { if (value == null) go back precise; Matcher m = zipPattern. matcher( price ); if (! m. matches()) go back fake; go back checker . isZipCodeValid(value); } } directory 3-27. america CDI Qualifier @Qualifier @Retention(RUNTIME) @Target({FIELD, style, METHOD}) public @interface united states { } notice within the subsequent chapters, you'll find tips to combine Bean Validation with different necessities reminiscent of JPA (you can upload constraints in your entities) or JSF (you can constrain your backing beans). Writing the CustomerIT and AddressIT Integration assessments How do we now attempt our constraints on our beans? We can’t quite write unit exams for @Email, because it is a constraints aggregation annotation, or for @ZipCode since it wishes injection to paintings (which is a box service). the best is to jot down an integration try out; that's, use the ValidatorFactory to get a Validator and validate our beans. directory 3-28 indicates the CustomerIT category that integration-tests the client bean. The init() strategy initializes the Validator (using the ValidatorFactory) and the close() technique releases the manufacturing unit. Then the category contains assessments: one making a legitimate buyer item and one other one developing an item with an invalid email deal with and checking even if the validation fails. directory 3-28. The CustomerIT Integration try out public type CustomerIT { deepest static ValidatorFactory vf; inner most static Validator validator; @BeforeClass public static void init() { vf = Validation. buildDefaultValidatorFactory() ; validator = vf. getValidator() ; } @AfterClass public static void close() { vf. close(); } @Test public void shouldRaiseNoConstraintViolation() { client consumer = new Customer("John", "Smith", " jsmith@gmail. com "); Set> violations = validator. validate(customer) ; assertEquals( zero , violations. size()); } @Test public void shouldRaiseConstraintViolationCauseInvalidEmail() { patron client = new Customer("John", "Smith", " DummyEmail "); Set> violations = validator. validate(customer) ; assertEquals( 1 , violations. size()); assertEquals("invalid electronic mail address", violations. iterator(). next(). getMessage() ); assertEquals("dummy", violations. iterator(). next(). getInvalidValue() ); assertEquals("{org. agoncal. booklet. javaee7. chapter03. e mail. message}", violations. iterator(). next(). getMessageTemplate() ); } } directory 3-29 follows an analogous trend (creating a Validator with a manufacturing facility, validating a bean, and shutting the manufacturing facility) yet for the tackle bean. directory 3-29. The AddressIT Integration attempt public category AddressIT { @Test public void shouldRaiseConstraintViolationCauseInvalidZipCode() { ValidatorFactory vf = Validation. buildDefaultValidatorFactory(); Validator validator = vf. getValidator(); deal with deal with = new Address("233 Spring Street", "New York", "NY", " DummyZip ", "USA"); Set> violations = validator.