Re: A few issues with HelloWorld WS sample

[scabooz]

Sebastien,

I have a slightly different perspective, inline below.

Dave

<snip>

2) What is the point of promoting it anyway? It seems the only point of

promoting it would be to allow this Composite to serve as the impl for
another component.
Since we don't do that in this simple sample, doesn't it just add
confusion?

It seems to be the SCDL should look something like this, ideally:

   <component name="HelloWorldServiceComponent">
     <implementation.java class="helloworld.HelloWorldServiceComponent"/>
     <reference name="helloWorldService">
       <binding.ws wsdlElement="
http://helloworld#wsdl.port(HelloWorldService/HelloWorldSoapPort)"/>
     </reference>
   </component>

What you're proposing is correct, but I think that the best practice should be to promote services and references that use bindings and go out of an SCA domain, to allow their bindings and endpoints to be reconfigured at deployment time, by using a deployment composite for example.

The spec introduced the ability to put bindings on component services
and references.  For top level components, that's where the bindings
should go (IMHO) as a best practice.  Promoted services and
references don't really have a meaning when a composite is included
(which is what happens at deployment). Just seems like extra baggage to
me.  I think it will be clear when a composite is developed, whether or
not it is intended to be deployed or used as an implementation.

Your perspective makes the assumption that all composites might one
day be used as an implementation.  I am taking the opposite position.
None of this is critical, as both are supported...just makes for good
discussion.


<snip>



---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]