[
https://issues.apache.org/jira/browse/OPENJPA-1787?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13451264#comment-13451264
]
Roger Keays commented on OPENJPA-1787:
--------------------------------------
I've hit this bug again with cascade merging. Validations on the nested object
fail because the fields are all null. Maybe the fireEvents flag isn't properly
handled when cascading?
> Bean validation fails merging a new entity
> ------------------------------------------
>
> Key: OPENJPA-1787
> URL: https://issues.apache.org/jira/browse/OPENJPA-1787
> Project: OpenJPA
> Issue Type: Bug
> Components: jpa, kernel
> Affects Versions: 2.0.1, 2.1.0, 2.2.0
> Reporter: Oliver Ringel
> Assignee: Jeremy Bauer
> Priority: Critical
> Fix For: 2.1.1, 2.2.0
>
> Attachments: com.example.TestEmployeeDAO.txt,
> OPENJPA-1787_2.1.x.patch, OPENJPA-1787_jUnits_2.1.x.patch, openjpa-1787.tar,
> testcase-openjpa-1787.tar
>
>
> The bean validation is not working correctly
> If you try to merge a new entity.
> EntityManager em = entityManagerFactory.createEntityManager();
> Person person = new Person();
> person.setName("Oliver"); //
> Employee.name is annotated @NotNull
> person = em.merge(person);
> you get a ConstraintValidationException, although name is set.
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira
