Discussions

EJB design: EJB and non-trransactiona DB

Bookmark and Share Get thread feed

  1. EJB and non-trransactiona DB (3 messages)

    • Posted by: Joao Galamba
    • Posted on: April 25 2002 14:50 EDT
    Hi everybody,

    I want to access a non-transactional DB via JDBC.
    Actually, the JDBC driver is somekind of a wrapper
    to the DB objects. It doesn't support transactions
    (commits, so we can't have rollbacks).
    Should I use EJBs in this case? Can a EJB help me
    here in dealing with transactions?
    Thanks in advance.
    Reply to this

    Threaded Messages (3)

  2. EJB and non-trransactiona DB[ Go to top ]

    Hi
    It is very much clear that EJB container takes help of DB for transaction. If your DB does not supprt transaction , then the driver for that database can also not support transaction. In a transaction many parties are involved
    1- ur Componant
    2- Container
    3- DB Driver
    4- DB
    If any of these party does not support transaction then u can not use transaction.
    Reply to this Reply to original

  3. EJB and non-trransactiona DB[ Go to top ]

    Weblogic supports three concurrency strategies on Entity EJBs. Exclusive, Database and ReadOnly.

    The default behavour up to 5.1 was exclusive. This locked people out of the Entity Bean until the transaction completed. For a non transaction DB and a stand alone server this would work.

    For 6.1 onwards Weblogic defaults to Database. This passes the locking request onto the database.

    Reply to this Reply to original

  4. EJB and non-trransactiona DB[ Go to top ]

    The solution could be having a batch read from this non-transactional data source and storing it in a normal database.
    Reply to this Reply to original