We're updating the issue view to help you get more done. 

@Email reported as "disallowed" for String field

Description

Upgrading from 4.2.0.Final to 4.3.0.Alpha1 caused the @Email annotation to be reported as "disallowed for this data type" for a String field.

@NotEmpty
@Email
private String emailAddress;

The annotation @Email is disallowed for this data type.

This seems like a really weird bug as I would expect there is a unit test case that tests that @Email is processed correctly, so I'm pondering the value of expending the effort of creating just such a simple example as a test case. Any suggestions on things I can do on my side to narrow/explore this issue before I create a full blown example? I tried a few variations like adding another String field and trying that and got the same message (no surprise).
Thanks!
Dan

Environment

Java 1.6, Windows 7, Maven 3.0.2

Status

Assignee

Unassigned

Reporter

Daniel Ford

Labels

None

Worked in

None

Feedback Requested

None

Feedback Requested By

None

backPortable

None

Community Help Wanted

None

Suitable for new contributors

None

Requires Release Note

None

Pull Request

None

backportDecision

None

backportReEvaluate

None

Components

Fix versions

Affects versions

4.3.0.Alpha1

Priority

Major