[ https://jira.jboss.org/jira/browse/ISPN-70?page=com.atlassian.jira.plugin... ] Vladimir Blagojevic resolved ISPN-70. ------------------------------------- Resolution: Done We agreed that the optimal solution, taking all trade offs into account, is to create a new interceptor. It just gets too messy if we subclass TxInterceptor since we have to then handle DistTxInterceptor and adding this functionality to LockingInterceptor blows it up quite a bit. Existing LockIterceptor#visitLockControlCommand (implemented for ISPN-48) has been augmented slightly to handle specific cases of implicit locking. A new interceptor was created - ImplicitEagerLockingInterceptor -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: https://jira.jboss.org/jira/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira