[
https://issues.apache.org/jira/browse/TUSCANY-3287?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Ramkumar Ramalingam resolved TUSCANY-3287.
------------------------------------------
Resolution: Fixed
Committed revision
820238
in 2.x.
> Improvements in implementation.spring module complaince with OASIS specs
> ------------------------------------------------------------------------
>
> Key: TUSCANY-3287
> URL: https://issues.apache.org/jira/browse/TUSCANY-3287
> Project: Tuscany
> Issue Type: Improvement
> Components: Java SCA Spring Implementation Extension
> Affects Versions: Java-SCA-2.0
> Reporter: Ramkumar Ramalingam
> Assignee: Ramkumar Ramalingam
> Fix For: Java-SCA-2.0
>
>
> Here is the list of items for improvement and for compliance with OASIS
> specs...
> 1. Use @id as bean name if set, else use the first name available from the
> @name attribute.
> 2. No explicit/implict service can be created for the following beans ....
> - <bean/> elements @class attribute is absent
> - <bean/> elements @abstract attribute value is set to "true"
> - <bean/> elements @factory-bean attribute value is set
> - <bean/> elements @factory-method attribute value is set
> - <bean/> elements @parent attribute value is set to reference another
> bean in the application context
> - <bean/> element is nested within another <bean/> element as inner
> bean.
> - <bean/> element @class attribute specifies the spring binary
> classes that starts with "org.springframework"
> 3. If present, all the Spring application context configuration files
> identified by the "Spring-Context" header in the MANIFEST.MF file MUST be
> collectively used to build the Spring application context for
> implementation.spring element.
> 4. If there is no MANIFEST.MF file or if there is no Spring-Context header
> within the MANIFEST.MF file, the Spring application context MUST be built
> using all the *.xml files in the META-INF/spring subdirectory within the JAR
> identified by the @location URI or underneath the directory specified by the
> @location URI.
> 5. The @target attribute of a <service/> subelement of a <beans/> element
> MUST have the value of the @name attribute of one of the <bean/> subelements
> of the <beans/> element.
> 6. Introspect the collection of references and properties.
> 7. Check for uniquess of the SCA elements defined in the Spring Application
> Context...
> - The value of the @name attribute of an <sca:service/> subelement
> of a <beans/> element MUST be unique amongst the <service/> subelements of
> the <beans/> element.
> - The value of the @name attribute of an <sca:reference/> subelement
> of a <beans/> element MUST be unique amongst the @name attributes of the
> <reference/> subelements, <property/> subelements and the <bean/> subelements
> of the <beans/> element.
> - The value of the @name attribute of an <sca:property/> subelement
> of a <beans/> element MUST be unique amongst the @name attributes of the
> <property/> subelements, <reference/> subelements and the <bean/> subelements
> of the <beans/> element.
> 8. Read @requires and @policySets from <sca:reference> and <sca:service>
> elements.
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
