Thanks for responding Raymond, That's not what I envisioned, and I'm struggling to find more concrete guidance in the OSOA specs.
Though closest guidance I saw in skimming the Assembly spec was on lines 1522-23: . The bindings defined on the component service are still in effect for local wires within the composite that target the component service This, to me, suggests that you would only have one WS endpoint, as far as the non-SCA world is concerned, though you have multiple ways of resolving an SCA reference wire target pointing to this service, from other SCA clients within the domain, depending on whether they are in the same composite (Composite2) as C2 or not. What are your reasons for understanding that there would be two web services here? Thanks, Scott On Mon, Mar 17, 2008 at 5:07 PM, Raymond Feng <[EMAIL PROTECTED]> wrote: > Here is my understanding: > > 1) Component C1 has a service named as svc1 with binding.ws. > 2) Component C2 has a service named as innerService with binding.ws. > > I assume two web services (one for the innerService, the other for svc1) > will be exposed when this composite is started. I don't think binding.sca > plays a role in your scenario. > > Thanks, > Raymond > > -------------------------------------------------- > From: "Scott Kurz" <[EMAIL PROTECTED]> > Sent: Monday, March 17, 2008 1:53 PM > To: <[email protected]> > Subject: real basic question on Composite impl (recursion) > > > I think this has been discussed before on this list.. but I'm not sure > or > > forget where we ended up. > > > > In the case that you have a non-default binding on a component service > > defined with an inner composite which > > is in turn used as a component impl, what happens if the service is not > > re-defined overridden at the higher level? > > > > As an example, in the following case, does the service C1/svc1 have a WS > > binding or default binding (or both)? > > > > <composite name="Composite1" xmlns:ns="http://dummy";> > > <component name="C1"> > > <implementation.composite name="ns:Composite2"> > > </component> > > </composite> > > > > <composite name="Composite2" targetNamespace="http://dummy"; xmlns:ns=" > > http://dummy";> > > <component name="C2"> > > <implementation.java class="my.C2Impl"> > > <service name="innerService"> > > <binding.ws .../> > > </service> > > </component> > > <!-- innerService of component C2 is promoted as svc1 --> > > <service name="svc1" promote="C2/innerService"/> > > </composite> > > > > Thanks, > > Scott > > > > --------------------------------------------------------------------- > To unsubscribe, e-mail: [EMAIL PROTECTED] > For additional commands, e-mail: [EMAIL PROTECTED] > >
