JBoss Adds Full Transaction Support 17
thedude79 writes "JBoss adds full transaction support by buying Arjuna - as listed in their product definition and the buyout announcement."
Mathematicians practice absolute freedom. -- Henry Adams
not now (Score:1)
Re:not now (Score:1)
Re:not now (Score:1)
Re:not now (Score:1, Informative)
question: why transactions in app server? (Score:2, Interesting)
Re:question: why transactions in app server? (Score:2)
You misunderstand J2EE (Score:1)
If you're doing your stored procedures and triggers in the J2EE server, that's just wrong. The result would be a weak, memory hogging duplicate of DB functionality. It's as
Re:You misunderstand J2EE (Score:2)
They cross DB boundaries (Score:5, Informative)
It's an "enterprise" thing. If your business is large enough to be horizontally partitioned into departments with seperate IT, then you'll probably need it. Otherwise, probably not.
Re:question: why transactions in app server? (Score:4, Informative)
Note that it's not only databases that use transactions, Slide f.e. can support transactions at the HTTP level.
What was absent before? (Score:1)
Re:What was absent before? (Score:1)
Re:What was absent before? (Score:4, Informative)
What Arjuna supports are WS-CAF [oasis-open.org] and WS-TX. These are protocols which abstract the implementation of transactions. They can be supported regardless of the data storage technology used by the application server.
Bringing these technologies into the open source world means that many enterprises will now be newly able to operate entirely without proprietary software technology, if they so choose. Enterprises ranging from webshops to Fortune 500s to national government departments.
Re:What was absent before? (Score:2, Informative)
They now have the facility to manage distributed transactions with logging and recovery, locally or via OTS.
See the Arjuna site for more details. http://www.arjuna.com/products/arjunats/index.html [arjuna.com]
Re:What was absent before? (Score:4, Informative)
The difficulties arise when you're doing operations that involve more than one database or a database and some other type of software. For example, say the business logic does two things: it updates a database record and it sends an SMS message to a mobile device informing it of the update. Ideally, you want to wrap those two operations in a single transaction, so that if the udpate fails no message gets sent and vice-versa. Of if the update succeeds but the system goes down then on wakeup the system continues and sends out the message, or else rolls back the whole thing.
That's what this stuff is about.
Eric
See your HTTP headers [ericgiguere.com]