[ https://issues.apache.org/jira/browse/OPENJPA-1787?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12908778#action_12908778 ] 

Oliver Ringel commented on OPENJPA-1787:
----------------------------------------

OK, I think I described the issue not clear enough.

As you said right, @NotNull should only throw an exception, if name is not set. 
The problem is, that I get an exception (javax.validation.ConstraintViolationException), 
although I called setName().

Using persist instead of merge is working as expected. I added added test method to 
demonstrate this.






> 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: validation
>    Affects Versions: 2.0.1, 2.1.0
>         Environment: Ubuntu 10.04, Spring 3.0.3
>            Reporter: Oliver Ringel
>         Attachments: openjpa-1787.tar
>
>
> The bean validation is not working correctly, if you try to merge not existing entity.
>         Employee employee = new Employee();
>         employee.setName("Oliver");                               // Employee.name is annotated @NotNull 
>         employee = em.merge(employee);
> em.persist and em.merge together with a managed entity is working as expected.

-- 
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.