On Tue, Sep 21, 2010 at 10:59 AM, Matthias Herbst <[email protected]> wrote: > Hi Simon! > > Thanks for your reply! > > I'm using the composite as top level composite. > When I put the service definition inside the component like this, it works: > <component name="RegistryComponent"> > <implementation.java > class="de.uniba.pipra.registry.impl.RegistryComponent"/> > <service name="AdministrationService"> > <interface.java > interface="de.uniba.pipra.registry.AdministrationService"/> > <binding.ws/> > </service> > <service name="LookupService"> > <interface.java interface="de.uniba.pipra.registry.LookupService"/> > <binding.ws/> > </service> > <service name="RegistrationService"> > <interface.java > interface="de.uniba.pipra.registry.RegistrationService"/> > <binding.ws/> > </service> > </component> > > But I don't receive any errors when I start it with the composite I posted > first. When I start the composite from above it starts but the Web service > does not start. and there is also no error. > The composite from above works when I do normal classpath dependencies to > all the jar files that are available in the tuscany-m5 build. > > Best regards, > matthias >
Ah OK, the promoted service are not exposed in this particular case as they don't have a meaning at the top level. Promoted servicesand references, only have a meaning if they are used by another component via implementation.composite. This is what the SCA assembly spec says about deploying composites into the domain level composite... 3979 10.7.1 add To Domain-Level Composite 3980 This functionality adds the composite identified by a supplied URI to the Domain Level Composite. The 3981 supplied composite URI refers to a composite within an installed contribution. The composite's installed 3982 contribution determines how the composite’s artifacts are resolved (directly and indirectly). The supplied 3983 composite is added to the domain composite with semantics that correspond to the domain-level 3984 composite having an <include> statement that references the supplied composite. All of the composites 3985 components become top-level components and the component services become externally visible 3986 services (eg. they would be present in a WSDL description of the Domain). The meaning of any promoted 3987 services and references in the supplied composite is not defined; since there is no composite scope 3988 outside the domain composite, the usual idea of promotion has no utility. Note the last sentence. Regards Simon -- Apache Tuscany committer: tuscany.apache.org Co-author of a book about Tuscany and SCA: tuscanyinaction.com
