This is not recommended. For what reason do you want to avoid transactions?
Thank you for answer, Alex!
Reasons - to avoid deadlocks and increase perfomance with cmp-operations.
I have non-crytical for dirty- or fantom- read entities. Why i need to use locking on each getField if I dont need locking instance (I think..)?
My Standard CMP 2.x EntityBeans use Require and QueuedPessimistic locking policy. If i use NoLock, there are problems with cmr, becouse they are need to access cmr fields in same tx, i understand...
Now (Require+QueuedPessimistickEJBLock), i have deadlocks with a get- methods and think maybe if i turn off transactions for selected get- methods,i'll can avoid deadlocks ?
but, as i am understand.. using cmp instance cache require transactions?
sorry fo my bad english..