Message Title

Adam Kędziora created an issue

Issue Type:	Bug
Affects Versions:	5.0.10
Assignee:	Unassigned
Created:	13/Jun/2017 10:28 AM
Environment:	Wildfly 10, oracle db
Priority:	Critical
Reporter:	Adam Kędziora

In my project I use Wildfly 10 and do the following :

 
                                                                @TransactionAttribute(TransactionAttributeType.REQUIRED)
public DtoOfMyVersionedEntityWithName sampleMethod(){
    MyVersionedEntityWithName e = em.find(MyVersionedEntityWithName.class,0l);
    em.lock(e, OPTIMISTIC_FORCE_INCREMENT);
    em.flush();
    return new DtoOfMyVersionedEntityWithName(e);
}
 
                                                            

the problem is that the version is not incremented on flush but on JTA transaction commit - which means that my dto doesn't have correct version information which is a major problem for me.

the same issue is also mentioned here: https://stackoverflow.com/questions/17785963/different-behavior-for-optimistic-force-increment-in-hibernate-4-2-vs-3-6

Add Comment

This message was sent by Atlassian JIRA