bean relationship

[ben oliver]

In my java classes, I have some relationship like

class A {

private B b;
private C c;

}

class B {

private C c;

}

class C {

private String name;
...
}

Then in the <bean> definition it will be like

<bean id="c" class="C">
<property name="name" value="xxxx"/>
</bean>

<bean id="b" class="B">
<property name="c" ref="c"/>
</bean>

<bean id="a" class="A">
<property name="b" ref="b"/>
<propery name="c" ref="c"/>
</bean>


Is this a good and reasonable design in Spring ? Does this work ?

[Jeanne Boyarsky]

Ben,
It looks fine. Assuming you have the relevant setters of course. (I understand you left them out for brevity; just mentioning in case someone takes the example literally.)

You don't have anything complex like a circular dependency. The only "wrinkle" I can think of is that you get the same instance of C injected into A and B unless you specify otherwise. Of course most of the time, having the same instance is fine.

[ben oliver]

thanks.