support declare a component definition with primary type #773
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.
Problem
When we want to declare an instance on the fly, the current logic uses the instance's class type as primary type for the bean definition.
But there are sometimes that we might expect using instance's supertype as primary type.
scoped(named("lifecycle")) { UserLifecycle1() as Lifecycle }
andsession2.declare(UserLifecycle2() as Lifecycle, qualifier = named("lifecycle"))
should achieve the same effect intuitively.Solution
I've changed the
Scope#declare
function and added aclazz
parameter to specify the primary type for current definition. InsideScopeDefinition#saveNewDefinition
, it will check ifclazz
is same as or supertype of providedinstance
.