jta

Why aren't nested transactions supported by JTA? Is it because of the complexity of implementing them (which I doubt) or some design principle? Stephen C (As @Piotr Nowicki points out, JTA does allow nested transactions, but this is optional not mandatory.) Why? This is one of those questions that is impossible to answer with any certainty, unless you were one of the people "in the room" when the decisions were made. It could be the inherent complexity of including nested transactions as part of the spec. Or apparent complexity at the time; i.e. they weren't sure they knew how to do a good job

I have a class with @Transactional annotation (instead of marking it for all of its method). Although i have a single method inside that class that shouldn't be annotated as @Transactional . My question is is there an annotation i can put in this method to mark it as "non-transactional"? or should i start marking each single method in this class as "transactional" excluding this method (a lot of work) thanks. Sotirios Delimanolis There are different transaction propagation strategies to use. These exist in the enum Propagation . The ones you might want to use are /** * Execute non

Is it possible to make XA-transactional access to the file system in Java? I want to manipulate files within the boundaries of a transaction and my transaction must participate in a distributed transaction via JTA (so I guess the file system needs to be accesses as a XAResource). I don't need support for fine-grained read/write file access; treating each file as a record is good enough for my needs. Does anybody know an open-source project that already does this? I don't feel like implementing this mess just to find out that it's already been done... I heard some rumors that JBoss Transcations

I have a springframework application in which I would like to add a transaction listener to a transaction which is currently in progress. The motivation is to trigger a post commit action which notifies downstream systems. I am using @Transactional to wrap a transaction around some service method -- which is where I want to create/register the post transaction listener. I want to do something "like" the following. public class MyService { @Transaction public void doIt() { modifyObjects(); // something like this getTransactionManager().registerPostCommitAction(new

We configure our Spring transaction in Spring config as: <tx:jta-transaction-manager/> I gather this means that Spring will automatically discover the underlying JTA implementation. So when we start up JBoss we see these messages while Spring searches: [JtaTransactionManager] [ ] No JTA TransactionManager found at fallback JNDI location [java:comp/Tran sactionManager] javax.naming.NameNotFoundException: TransactionManager not bound <<Big stack trace>> <<More of the same>> And then eventually see: [JtaTransactionManager] [ ] JTA TransactionManager found at fallback JNDI location [java:

An EJB method named Aby calls another EJB method named Bob Bob is marked with @TransactionAttribute(TransactionAttributeType.REQUIRES_NEW) When does bob transaction commits?: a) when bob invocation ends b) when aby invocation ends c) other. when? Petr Mensik I think A is right. When the method Bob is being called, it creates new transaction for it and method Aby gets suspended until the Bob transaction is committed. Also note that it has to be method from some other bean to make it transactional, methods called from the same bean do not act as a business methods. See this great article for

I'm developing a webapp which needs access to two different database servers (H2 and Oracle). The container is an Apache Tomee 1.5.1 and I'm using the Java EE stack with libraries provided in it (JSF, JPA, CDI, EJB, etc.). I'm trying to use two entity managers inside an XA transaction to extract data from the Oracle database and persist it in the H2 after transforming it, BUT all the queries are executed against the H2 database no matter the entity manager I use. Any help? EDIT : I found that if I try to access the entity managers in inverse order, they behavior is the same but accessing to

What is the difference between JTA and a local transaction? An example that shows when to use JTA and when to use a local transaction would be great. JTA is a general API for managing transactions in Java. It allows you to start, commit and rollback transactions in a resource neutral way. Transactional status is typically stored in TLS (Thread Local Storage) and can be propagated to other methods in a call-stack without needing some explicit context object to be passed around. Transactional resources can join the ongoing transaction. If there is more than one resource participating in such a