Support scoped proxy on mapper scan feature #484
Merged
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.
Fixes gh-476
By this change, the develop become can specified scope of mapper using mapper scan feature option and scope annotation(
@Scope
,@RefreshScope
, etc ...).The
defaultScope
apply to the mapper bean(MapperFactoryBean
) when scope of scanned bean definition issingleton
(default scope) and create a scoped proxy bean for scanned mapper when final scope is notsingleton
.Usage option on mapper scan feature
The developer can specify the scope of mapper bean that not specified scope annotation using option of mapper scan feature.
Using
@MapperScan
Using
MapperScannerConfigurer
Using XML Namespace(
<mybatis:scan/>
)Using scope annotation
The developer can specify the scope per mapper using scope annotation.