Add tip clarifying that @Transactional is not applicable to @BeforeClass methods #456
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
This tip is needed because when using
@BeforeClass
with TestNG tests unlike JUnit by the time@BeforeClass
is called the whole application context is setup and and dependency injection is working therefore as a user it easy to assume that @transactional should be working but it dose not work and then you waste lots of time trying to figure out why, until you make a call toTransactionSynchronizationManager.isActualTransactionActive()
and discover that@Transactional
is not supposed to be used with@BeforeClass
when working with TestNGFor example