Thanks for the update Ram
> > Simon, you had suggested that we should be looking back at the component in > the SCDL to see what has actually been defined as a reference and what has > been defined as a service and using this information to build the component > type. Does this comply with the specs, do we follow such model for other > implementation types? > > > I was looking at these words in section 2.1 of the latest version of the OASIS spec I have... "The SCDL also contains the <reference> element named “SCAReference”. The reference name becomes an addressable name within the Spring application context – so, in this case, “SCAReference” can be referred to by bean “Y” in the Spring configuration above." In particular "The reference name becomes an addressable name within the Spring application context" which I took to mean that the runtime uses reference information from the SCDL file to define an addressable name in the Spring context in order that it can then resolve bean refs approrpiately. In the context of this particular problem we can look into the SCDL for the references and properties that are defined there and hence determine which bean refs are references and which ones are properties. Regards Simon
