EJB Transaction Attribute

[Ariram Kalimuthu]

Hi Folks,
i need a clarification on below Transactionattributre in EJB 3

@TransactionAttribute(TransactionAttributeType.REQUIRES_NEW)

EJB container will create the new tarnsaction for any requests, if we use the above attribute.

My Question is,
It is required to use for only insert, delete,and update operation from database.
shall we use for fetch(select * from table) operation in database?

ie., if we use the for fetching operation, container will create new transaction.

JTA will be taking care about rollback/commit related operations.
but my case there is no chance to happen rollback operation

Please suggest me to shall i go a head to use this attribute in my EJB ot not?

Thanks in Advance!

[Ralph Jaus]

If there are only reading operations from a database and no other resources hava to be synchronized then it's better not to use transactions in the concerning ejb method. It's not only JTA overhead but also overhead for maintaining the persistence context (if you're using JPA).

Transaction attributes that prevent using transactions are NEVER and NOT_SUPPORTED. But in general it's safer to use NOT_SUPPORTED.