]
hantsy bai commented on SEAMPERSIST-69:
---------------------------------------
I will verify if it is disappeared in my project later, I always use em.flush WITHOUT
@Transactional for method due to this problem.
Transacation is problematic when save data
------------------------------------------
Key: SEAMPERSIST-69
URL:
https://issues.jboss.org/browse/SEAMPERSIST-69
Project: Seam Persistence
Issue Type: Bug
Reporter: hantsy bai
Priority: Critical
I used a ConversationScoped bean to save/update data. but it is very strange, when I edit
the data and want to update the data, the result was not saved successfully.
When I added @Transactional to the save the method, the same result.
When I added em.flush in the save method(with @Transactional annotation), I got an
exception, please refer to the forum post.
When I used em.flush standalone(without @Transactional annotation), it works well.
In before Seam2 application, all above worked well.
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators: