Question

也许,我做了一些错误的事情,但我无法为以下局势找到一个很好的办法。

我愿用Spring Batch underneath执行职务。工作通过预设的<条码>AsyncTaskExecutor在单独的校对进行。在我的单位试验中,我要:

Create few domain objects and persist them via DAO
Invoke the service method to launch the job
Wait until the job is completed
Use DAO to retrieve domain objects and check their state

显然,以上所有事项都应在一次交易中执行,但不幸的是,

我想到的想法:

Commit the transaction#1 after step (1). Is not good, as the DB state should be rolled back after the unit test.
Use Isolation.READ_UNCOMMITTED in job configuration. But this requires two different configurations for test and for production.

Answer 1

我认为,最简单的解决办法是,在试验执行期间,将“Launcher”与“SyncTaskExecutor”混为一谈,这样,工作就与测试和分享交易一样。

任务执行者组合可移至单独的春季配置Xml文档。有两个版本:一个是试验期间使用的SyncTaskExecutor,另一个是供生产使用的AsyncTaskExecutor。

Answer 2

虽然这不是解决你问题的真正办法,但我发现,有可能在工人体力行内启动new交易。在某些情况下,这可能是不够的。

资料来源:。

例:

@PersistenceContext
private EntityManager entityManager;
@Autowired
private PlatformTransactionManager txManager;

/* in a worker thread... */
public void run() {
    TransactionStatus tx = txManager.getTransaction(new DefaultTransactionDefinition());
    try {
        entityManager.find(...)
        ...
        entityManager.flush(...)
        etc...
        txManager.commit(tx);
    } catch (RuntimeException e) {
        txManager.rollback(tx);
    }
}

Answer 3

如果你确实想要不同的组合,我就建议把孤立政策排在你的组合中,将其价值从财产档案中去掉,以便你不要用一套不同的春季会议来进行测试和推测。

But I agree that using the same policy production uses is best. How vast is your fixture data, and how bad would it be to have a setUp() step that blew away and rebuilt your data (maybe from a snapshot, if it s a lot of data) so that you don t have to rely on rollbacks?

友情链接