On Fri, Dec 5, 2008 at 3:26 PM, fahim salim <[EMAIL PROTECTED]> wrote:
> Hi > > If you have some informations they are welcome. > > Thanks > Fahim > > 2008/11/28 fahim salim <[EMAIL PROTECTED]> > > Hello All >> >> >> As far as I understood, the Tuscany runtime is composed of core and >> extensions. >> >> I'd like to know if the core act as container to resolve the dependency >> injection mecanism used in Tuscany? >> >> Also, I'd like to know if there is redundancy of informations between >> annotations in the java files and the composite file ? >> >> For exemple, could it be possible to use only <service name=.../> or >> <reference name=.../> in composite file and not to use @Service and >> @Reference annotations in the source files ? >> >> >> Fahim >> >> > > Hi Fahim Again, apologies that this didn't get answered sooner. The core and extensions come together to form the Tuscany SCA runtime. The extensions allows people to add runtime extensions for things like bindings, implementation types, interfaces etc. All the sort of things you would expect to be extensible. The Java introspection and injection logic can be found in the implementation-java and implementation-java-runtime extensions. A java file used as a component implementation can describe a component type in three ways. 1/ using default rules to determine services, references and properties directly from the plain Java code 2/ using annotations in the java file itself to define services, references and properties. 3/ using a .componentType side file that contains XML also describing services, references and properties The component type describes the shape of the component. The information that you include in the composite file is used to configure the component. So using approach 1/ above it is possible to write Java component implementations without annotations and then configure them using the composite file. Regards Simon
