Spring SCA specification should accomodate common beans/aspects used by
different composites/components
-------------------------------------------------------------------------------------------------------
Key: TUSCANY-2162
URL: https://issues.apache.org/jira/browse/TUSCANY-2162
Project: Tuscany
Issue Type: New Feature
Components: Java SCA Spring Implementation Extension
Reporter: Catalin Boloaja
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 ?
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
