1. Explain the transactional attribute Bean-managed?

Bean-managed: Bean-managed transactions include any stateful or stateless session beans with a transaction-type set to Bean. The bean specifies the transaction demarcations using the javax.transactin.UserTransaction interface.

2. Explain the transactional attribute Never?

Never: When the methods that are not capable of participating in transactions are not accessible by a transactional client, Never is used.

3. Explain the transactional attribute NotSupported?

NotSupported: At the time of enterprise bean access a resource manager with or without the support of the external transaction coordination or not supported by the J2EE product, the NotSupported attribute is used.

4. Explain the transactional attribute Supports?

Supports: Supports attribute when the methods do not change database or update the atomicity without the concern of the update of the transaction.

5. Explain the transactional attribute Mandatory?

Mandatory: In the situation when the method absolutely requires an existing transaction.

6. Explain the transactional attribute RequiredNew?

RequiredNew: RequiredNew is used when the required results of the transactions to be committed irrespective of the caller's transactions.

7. Explain the transactional attribute Required?

Required: This is the default transaction attribute that ensures the methods are invoked within Java Transaction API transaction context. Required makes the transactional context used by the bean. If not the new context will be created.

8. Can you please explain demarcation and types of demarcation, declarative and programmatic demarcation?

Demarcation specifies a limit for a bean managed transaction, i.e. once a transaction begins, it ends with either commit or abort the key points of who issues begin and who issues commit or abort is called demarcating transactional boundaries.

Declarative Demarcation
Declarative transaction demarcation is also known as Container-Managed Transaction. The container demarcates different transactions as per the requirements specified by the application assembler in deployment descriptor. These instructions are called as transaction attributes.

Programmatic Demarcation
Programmatic Demarcation can also be called as Bean-Managed Transaction, the bean code that demarcates using the javax.transaction.UserTransaction interface.

The resources are accessed between javax.transaction.UserTransaction.begin() and javax.transaction.UserTransaction.commit(). This access makes the part of the transaction. The resource and resource manager declared in the deployment descriptor.

9. What is Programmatic Demarcation?

Programmatic Demarcation can also called as Bean-Managed Transaction. The bean code that demarcates using the javax.transaction.UserTransactijon interface.

10. What is Declarative Demarcation?

Declarative transaction demarcation is also known as Container-Managed Transaction. The container demarcates different transactions as per the requirements specified by the application assembler in deployment descriptor. These instructions are called as transaction attributes.

Download Interview PDF