Hi,
I think the base URI for a scheme cannot be global to a SCA domain. As you
said, that would be useless. The spec needs some clarifications here.
We might have two options here:
1) The SCA domain defines the base URI pattern such as http://$host:8080/.
And $host will be replaced by the running server name or address.
2) The baseURI is defined per runtime/server
(http://www.mail-archive.com/[email protected]/msg18613.html).
Thanks,
Raymond
----- Original Message -----
From: "Jean-Sebastien Delfino" <[EMAIL PROTECTED]>
To: <[email protected]>
Sent: Wednesday, June 06, 2007 1:51 PM
Subject: What's an SCA domain base URI? was: Servlet path change?
[snip]
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
I took another look at the spec, and you're correct this is what it says,
but now I am not sure I understand anymore how this can really work...
Well, maybe I do understand some of it, but I'd like to explore and
challenge it a bit here :)
I have a simple use case in mind:
- my SCA domain includes components running on two servers (an SCA domain
is a administrative domain so I'm going to assume that I have at least 2
servers in that domain)
- the host names of my two servers are servera and serverb
- my components provide web services, over the HTTP protocol
- what should my SCA domain URI look like? http:// and then what? just
http://? how is this domain URI useful here?
Possible answers:
- configure my domain URI to www.mydomain.com and have my two servers
appear as one... under www.mydomain.com/x and www.mydomain.com/y?
- conclude that domain URI is not so useful after all?
- another idea?
Thoughts?
--
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]
