3:58 p.m.
@Email reported as "disallowed" for String field
------------------------------------------------
Key: HV-567
URL: https://hibernate.onjira.com/browse/HV-567
Project: Hibernate Validator
Issue Type: Bug
Components: annotation-processor
Affects Versions: 4.3.0.Alpha1
Environment: Java 1.6, Windows 7, Maven 3.0.2
Reporter: Daniel Ford
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
--
This message is automatically generated by JIRA.
For more information on JIRA, see: http://www.atlassian.com/software/jira
4:30 p.m.
New subject: [Hibernate-JIRA] Assigned: (HV-567) @Email reported as "disallowed" for String field
[
https://hibernate.onjira.com/browse/HV-567?page=com.atlassian.jira.plugin...
]
Gunnar Morling reassigned HV-567:
---------------------------------
Assignee: Gunnar Morling
@Email reported as "disallowed" for String field
------------------------------------------------
Key: HV-567
URL: https://hibernate.onjira.com/browse/HV-567
Project: Hibernate Validator
Issue Type: Bug
Components: annotation-processor
Affects Versions: 4.3.0.Alpha1
Environment: Java 1.6, Windows 7, Maven 3.0.2
Reporter: Daniel Ford
Assignee: Gunnar Morling
Fix For: 4.3.0.Beta1
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
--
This message is automatically generated by JIRA.
For more information on JIRA, see: http://www.atlassian.com/software/jira
4:30 p.m.
New subject: [Hibernate-JIRA] Updated: (HV-567) @Email reported as "disallowed" for String field
[
https://hibernate.onjira.com/browse/HV-567?page=com.atlassian.jira.plugin...
]
Gunnar Morling updated HV-567:
------------------------------
Fix Version/s: 4.3.0.Beta1
@Email reported as "disallowed" for String field
------------------------------------------------
Key: HV-567
URL: https://hibernate.onjira.com/browse/HV-567
Project: Hibernate Validator
Issue Type: Bug
Components: annotation-processor
Affects Versions: 4.3.0.Alpha1
Environment: Java 1.6, Windows 7, Maven 3.0.2
Reporter: Daniel Ford
Assignee: Gunnar Morling
Fix For: 4.3.0.Beta1
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
--
This message is automatically generated by JIRA.
For more information on JIRA, see: http://www.atlassian.com/software/jira
4:38 p.m.
New subject: [Hibernate-JIRA] Commented: (HV-567) @Email reported as "disallowed" for String field
[
https://hibernate.onjira.com/browse/HV-567?page=com.atlassian.jira.plugin...
]
Gunnar Morling commented on HV-567:
-----------------------------------
Hi, thanks for reporting that issue. I can reproduce it. I think it's caused by
HV-484, there we changed the way how HV-specific constraints are linked to their
validator. Previously this happend via {{(a)Constraint(validatedBy=EmailValidator.class)}}
as for any other custom constraint, now the validator is registered automatically in order
to avoid referencing the internal {{constraintvalidators}} package from the public
{{constraints}} package. I've forgotten to adapt the annotation processor as well,
which I didn't notice as there is a test case for the handling of custom constraints
but not for HV-provided custom constraints.
@Email reported as "disallowed" for String field
------------------------------------------------
Key: HV-567
URL: https://hibernate.onjira.com/browse/HV-567
Project: Hibernate Validator
Issue Type: Bug
Components: annotation-processor
Affects Versions: 4.3.0.Alpha1
Environment: Java 1.6, Windows 7, Maven 3.0.2
Reporter: Daniel Ford
Assignee: Gunnar Morling
Fix For: 4.3.0.Beta1
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
--
This message is automatically generated by JIRA.
For more information on JIRA, see: http://www.atlassian.com/software/jira
4:45 p.m.
New subject: [Hibernate-JIRA] Commented: (HV-567) @Email reported as "disallowed" for String field
[
https://hibernate.onjira.com/browse/HV-567?page=com.atlassian.jira.plugin...
]
Daniel Ford commented on HV-567:
--------------------------------
That's great, thanks. I'll give it a try when Beta1 is released (soon I think).
Dan
@Email reported as "disallowed" for String field
------------------------------------------------
Key: HV-567
URL: https://hibernate.onjira.com/browse/HV-567
Project: Hibernate Validator
Issue Type: Bug
Components: annotation-processor
Affects Versions: 4.3.0.Alpha1
Environment: Java 1.6, Windows 7, Maven 3.0.2
Reporter: Daniel Ford
Assignee: Gunnar Morling
Fix For: 4.3.0.Beta1
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
--
This message is automatically generated by JIRA.
For more information on JIRA, see: http://www.atlassian.com/software/jira
5:45 p.m.
New subject: [Hibernate-JIRA] Updated: (HV-567) @Email reported as "disallowed" for String field
[
https://hibernate.onjira.com/browse/HV-567?page=com.atlassian.jira.plugin...
]
Gunnar Morling updated HV-567:
------------------------------
Pull Requests: https://github.com/hibernate/hibernate-validator/pull/113
@Email reported as "disallowed" for String field
------------------------------------------------
Key: HV-567
URL: https://hibernate.onjira.com/browse/HV-567
Project: Hibernate Validator
Issue Type: Bug
Components: annotation-processor
Affects Versions: 4.3.0.Alpha1
Environment: Java 1.6, Windows 7, Maven 3.0.2
Reporter: Daniel Ford
Assignee: Gunnar Morling
Fix For: 4.3.0.Beta1
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
--
This message is automatically generated by JIRA.
For more information on JIRA, see: http://www.atlassian.com/software/jira
5:57 p.m.
New subject: [Hibernate-JIRA] Resolved: (HV-567) @Email reported as "disallowed" for String field
[
https://hibernate.onjira.com/browse/HV-567?page=com.atlassian.jira.plugin...
]
Hardy Ferentschik resolved HV-567.
----------------------------------
Resolution: Fixed
@Email reported as "disallowed" for String field
------------------------------------------------
Key: HV-567
URL: https://hibernate.onjira.com/browse/HV-567
Project: Hibernate Validator
Issue Type: Bug
Components: annotation-processor
Affects Versions: 4.3.0.Alpha1
Environment: Java 1.6, Windows 7, Maven 3.0.2
Reporter: Daniel Ford
Assignee: Gunnar Morling
Fix For: 4.3.0.Beta1
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
--
This message is automatically generated by JIRA.
For more information on JIRA, see: http://www.atlassian.com/software/jira
4558
days inactive
4562
days old
hibernate-issues@lists.jboss.org
6 comments
3 participants
participants (3)
-
Daniel Ford (JIRA) -
Gunnar Morling (JIRA)
-
Hardy Ferentschik (JIRA)