Hi,
Please see my comments inline below.
Thanks,
Raymond
----- Original Message -----
From: "Jean-Sebastien Delfino" <[EMAIL PROTECTED]>
To: <[email protected]>
Sent: Wednesday, June 06, 2007 1:09 PM
Subject: Re: Servlet path change?
[snip]
Raymond Feng wrote:
Hi, Ant.
I agree with you that we should generalize the service binding URI. I
think I have a proposal here.
When the CompositeBuidler builds the composite, we should calculate the
service binding URI based on various pieces of the information as defined
by the spec and save the effective URI in the service binding so that
Binding.getURI() will return the good URI. This way, the binding
providers doesn't have to deal with the calculation.
If you guys think it's the right way to go, I can try to add the function
to the CompositeBuilder.
This is also related to how a binding is mapped to a protocol (scheme)
and baseURI. The topic is being discussed on the ML under "SCA Binding
and Distribution".
Thanks,
Raymond
This initially sounds reasonable to me, but how are you going to handle
protocol/binding specific URIs in CompositeBuilder? not all binding URIs
start with http://...
That's where the SCA domain configuration of base URIs for hierarchical URI
scheme comes to play. The SCA spec says: "An SCA domain should define a base
URI for each hierarchical URI scheme on which it intends to provide
services".
Let's assume we have two bindings: binding.x and binding.y. The scheme
(protocol) is "ftp" for binding.x and "http" for binding.y.
<component name="C1">
<service name="FTPService">
<binding.x .../>
</service>
<service name="HTTPService">
<binding.y .../>
</service>
</component>
If the SCA domain defines the mapping:
binding.x --> ftp://ftp.example.com/public
binding.y --> http://www.example.com
Then the computedURI for binding.x and binding.y would be:
binding.x: ftp://ftp.example.com/public/C1/FTPService
binding.y http://www.example.com/C1/HTTPService
The CompositeBuilder should compute and keep them in the binding. We can add
computedURI as you proposed.
Would it be possible to let the Binding extension decide what form the URI
should take?
Maybe we could have have another field on the base Binding named
computedURI (computed by CompositeBuilder), which the binding extension
could use to compose the value of the actual URI field?
--
Jean-Sebastien
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
