Slashdot Mirror

← Back to Stories (view on slashdot.org)

JBoss Adds Full Transaction Support

Posted by Hemos on from the suiting-up-for-battle-wtih-Big-Blue dept.

thedude79 writes "JBoss adds full transaction support by buying Arjuna - as listed in their product definition and the buyout announcement."

6 of 17 comments (clear)

  1. They cross DB boundaries by Julian+Morrison · · Score: 4, Informative

    A typical use of J2EE transactions would be an app that needs to modify in-memory objects, modify local SQL data, modify remote data via a defined abstract interface with limited permissions, and do it all as one transaction, succeed or fail atomically. J2EE transactions make that possible, and in some cases easy.

    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.

  2. Re:question: why transactions in app server? by GuyWithLag · · Score: 3, Informative

    These kinds of tech are necessary when you aggregate several "products" into a "solution", each "product" requiring its own database or database-like system. This gives you recoverable transactions across databases (well, usually).

    Note that it's not only databases that use transactions, Slide f.e. can support transactions at the HTTP level.

  3. Re:What was absent before? by aminorex · · Score: 3, Informative

    That's just wrong.

    What Arjuna supports are WS-CAF 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.

    --
    -I like my women like I like my tea: green-
  4. Re:What was absent before? by Eric+Giguere · · Score: 3, Informative

    All application servers are transactional in the simple case, where all the operations actually affect a single database. In that case the application server's transaction maps to the database server's concept of a transaction and things are very simple.

    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

  5. Re:What was absent before? by Kevin+Conner · · Score: 2, Informative
    CAF and TX support is only a part of the acquisition, JBoss have also acquired the JTA and JTS implementations.

    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

  6. Re:not now by Anonymous Coward · · Score: 1, Informative

    Actually, Arjuna's transaction manager has worked with JBoss for years. What's new is that it will now be open source.