Home/ Questions/Q 785901
In Process

The Archive Base Latest Questions

Editorial Team
  • 0
Asked: 2026-05-14T20:57:11+00:00

I am developing an application using Eclipselink and as part of the app I

  • 0

I am developing an application using Eclipselink and as part of the app I need to be able to manipulate some of the objects which involves changing data without it being persisted to the database (i merging/changing objects for some batch generation processes).

I am reluctant to change the data in the Entity objects, as there is a risk that even though i have not marked the methods as @Transactional, this method could in the future be inadvertantly called from within a transactional method and these changes could be persisted.

So my question is, is there anyway to get around this? Such as force a method to always be non-transactional regardless; terminate any transactionality as soon as the method is started; etc.

I know there is a .detach() method that can detach the objects from the Entity Manager, however, there are many objects and this seems like a potentially error prone fail-safe on my code.

Share

Leave an answer

You must login to add an answer.

Need An Account,

1 Answer

  1. Editorial Team

    If this is spring, you have

    @Transactional(propagation=Propagation.NOT_SUPPORTED)

    Execute non-transactionally, suspend the current transaction if one exists. Analogous to EJB transaction attribute of the same name.

    If it’s EJB, you have a transaction attribute of the same name.

    Anyway, instead of playing around with transactions, you can simply clone your object and modify the required data. Deep cloning can be achieved via commons-lang SerializationUtils.

    • 0