[sca-j] ISSUE-175: Updated Proposal

Important points to note from Spring Documentation:
(just for information, not for the proposal)

When using XML-based configuration metadata,
you use the 'id' or 'name' attributes to specify the bean identifier(s).
The 'id' attribute allows you to specify exactly one id, and as it is a
real XML element ID attribute, the XML parser is able to do some extra
validation when other elements reference the id; as such, it is the preferred
way to specify a bean id.

Please note that you are not required to
supply a name for a bean. If no name is supplied explicitly, the container
will generate a unique name for that bean. The motivating use case for
not supplying a name for a bean is inner beans.

In Spring you can have ApplicationContexts
form a hierarchy, one contexts is said to be the parent of another one.
In case of multiple application context, later bean definitions will override
ones defined in earlier loaded files. This can be leveraged to deliberately
override certain bean definitions via an extra XML file.

Updated Proposal:

The SCA Spring Component Implementation specification
should state that... 

If there are no <sca:service/> elements
in the application context, one <service/> element exists for each
service implemented by each top-level <bean/> element in the application
context whose "id" attribute is available. Every bean that needs
to be considered for implicit services within the application context should
have "id" attribute associated with it which uniquely identifies
the bean, beans with no "id" attribute will be ignored.

In case of multiple application context hierarchy,
where one context is said to be the parent of another one, the later bean
definition will override ones defined in the earlier loaded files. Applying
this rule, implicit services will be created for the later bean definition
which will override the ones defined in the earlier loaded files.

Thanks & Regards,

R Ramkumar

Open Source SOA Development - Apache Tuscany

Phone : 91-80-41927623

Email  :