xml-parent vs. No equivalent Annotation [SPR-5580]

[spring-projects-issues]

Paul Bacsik opened SPR-5580 and commented

This works:
<bean id="parentBean" class="AbstractCls" abstract="true"><property name="setter" value="basicString"/>....
<bean class="SubClsExtendsAbstractCls" parent="parentBean"> ...

This does not work - setter is not called:
<bean id="parentBean" class="AbstractCls" abstract="true"><property name="setter" value="basicString"/>....
@Component public class SubClsExtendsAbstractCls extends AbstractCls { ...

Nice would be:
@Component(parent="parentBean")

---

Affects: 2.5.6

Sub-tasks:

• Annotation for xml-parent - Solution [SPR-6343] #11009 Annotation for xml-parent - Solution

5 votes, 6 watchers

[spring-projects-issues]

Eugen Paraschiv commented

Is there any new development on this? It seems like a basic configuration requirement.
Thanks.

[spring-projects-issues]

Roberto Ruiz commented

@ChildOf solution proposed in sub-task is probably the best one.
That way, there is no need to add the "parent" attribute if you have made your own stereotypes

[spring-projects-issues]

Stéphane Nicoll commented

Check this thread

[spring-projects-issues]

xorcus commented

I have a situation where a given interface is implemented by arbitrary service provides. All implementations of the interface are being autowired into a component using them. This is the original product.

Now external to this, I have a customization project which needs to customize the behavior of one specific service provider implementation provided by the original product, but without touching its original source code (the original product is added to classpath as a jar). Effectively, I need to create another component implementing the same interface, but instead of adding it to the bunch of existing implementations, I need to instruct spring to use the original one as a parent, and still preserve its id. In other words, replace the original service provider instance with a customized version without affecting any other implementation.

I believe the description from the linked thread does not cover such a case and the need for @Component(parent=...) or @ChildOf() still exists.