Page History

...

The use case : service composites using components or composites as Spring beans. Those beans rely on other injected common beans or applied aspects.
We should not instantiate a new bean or aspect for every Spring component or composite if the beans and aspects are shared .
The Spring way would be to declare a parent context to accommodate the common beans / aspects.
The Spring SCA implementation specification says a new Spring context will be created for each composite. Unclear for component.
Can we enhance the specification in the sense of a parent application context ?

Ramkumar 10/10/2008: http://blog.springsource.com/2007/06/11/using-a-shared-parent-application-context-in-a-multi-war-spring-application/^{Image Removed}