Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Jump to bottom

Make sure JpaAfterClearFlusher is registered if an EntityManager exists #6

Closed
robert-bor opened this issue Oct 25, 2017 · 0 comments
Closed

Make sure JpaAfterClearFlusher is registered if an EntityManager exists #6

robert-bor opened this issue Oct 25, 2017 · 0 comments
Assignees
@robert-bor
Labels
enhancement

Comments

@robert-bor
Copy link
Contributor

See the raison d'etre for the AfterClearFlusher concept.

The starter must ascertain the JpaAfterClearFlusher is instantiated with the EntityManager and registered to BeanMapper.
@robert-bor robert-bor self-assigned this Oct 25, 2017
robert-bor added a commit that referenced this issue Oct 25, 2017
@robert-bor
Make sure JpaAfterClearFlusher is registered if an EntityManager exists
c500489 
Issue #6 when JPA is in play, make sure to register the JpaAfterClearFlusher with a valid EntityManager. This will be added to the flush-chain, to be potentially executed when flushAfterClear is turned on. This can be either set on BeanCollection or the override configuration.

Note that @PersistenceContext cannot be used in the auto-configuration, since this will fail the tests. Instead optional @Autowired is used.
robert-bor added a commit that referenced this issue Oct 25, 2017
@robert-bor
Make sure JpaAfterClearFlusher is registered if an EntityManager exists
747a8ed 
Issue #6 when JPA is in play, make sure to register the JpaAfterClearFlusher with a valid EntityManager. This will be added to the flush-chain, to be potentially executed when flushAfterClear is turned on. This can be either set on BeanCollection or the override configuration.

Note that @PersistenceContext cannot be used in the auto-configuration, since this will fail the tests. Instead optional @Autowired is used.
@robert-bor robert-bor mentioned this issue Oct 25, 2017
Merged
robert-bor added a commit that referenced this issue Oct 25, 2017
@robert-bor
Make sure JpaAfterClearFlusher is registered if an EntityManager exists
0dad87c 
Issue #6 when JPA is in play, make sure to register the JpaAfterClearFlusher with a valid EntityManager. This will be added to the flush-chain, to be potentially executed when flushAfterClear is turned on. This can be either set on BeanCollection or the override configuration.

Note that @PersistenceContext cannot be used in the auto-configuration, since this will fail the tests. Instead optional @Autowired is used.
robert-bor added a commit that referenced this issue Oct 25, 2017
@robert-bor
Make sure JpaAfterClearFlusher is registered if an EntityManager exists
342b120 
Issue #6 when JPA is in play, make sure to register the JpaAfterClearFlusher with a valid EntityManager. This will be added to the flush-chain, to be potentially executed when flushAfterClear is turned on. This can be either set on BeanCollection or the override configuration.

Note that @PersistenceContext cannot be used in the auto-configuration, since this will fail the tests. Instead optional @Autowired is used.
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees

@robert-bor robert-bor

Labels
enhancement
Projects
None yet
Milestone
No milestone
Development

No branches or pull requests
1 participant
@robert-bor