A few more comments and ideas.
[snip]
scabooz wrote:
+1 to Scott's point. The spec does not assert that services are only
available outside of a Domain when they are promoted as composite level
services.
Dave
----- Original Message ----- From: "Scott Kurz" <[EMAIL PROTECTED]>
To: <[email protected]>
Sent: Thursday, May 17, 2007 3:51 PM
Subject: Re: Promoting and configuring services in an SCA domain, was:
A few issues with HelloWorld WS sample
Sebastien,
I'm interested how it would matter whether you promoted it or not?
If you have a non-default binding on a component-level service that
it is
visible to
"the world" already. And I thought the default binding was not
intended
to allow you to
cross domain boundaries.
Yes, a service on a top level component, with a non-default binding is
visible outside the domain. I don't have an issue with this case. That
pattern is supported and I have modified the HelloWorldWS sample to use it.
I have issues with the use of bindings on services offered by components
in nested composites, but that's probably a different discussion...
The deployed composite which contributed this component to the domain
can be
updated if you
wish to modify the deployed component (so you don't need the domain
composite level service to do so).
I'm not sure I understand what you're proposing to update the composite
containing the component and its service and binding declarations. Are
you talking about using a "deployment composite" as described in the
spec in "1.10.4.2 add Deployment Composite & update Deployment
Composite" or are you thinking about opening the SCA contribution,
changing the composite inside the contribution, and
updating/reinstalling it as described in "1.10.4.1 install Contribution
& update Contribution"?
--
Jean-Sebastien
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
