Good points. +1 to have separate modules handle the physical topology
aspect.
Thanks,
Raymond
----- Original Message -----
From: "Jean-Sebastien Delfino" <[EMAIL PROTECTED]>
To: <[email protected]>
Sent: Wednesday, June 06, 2007 3:46 PM
Subject: Re: Servlet path change?
Raymond Feng wrote:
Hi,
I agree with you that the base URIs are from the topology model. What I
meant before is that the CompositeBuilder will be aware of the topology
model and use it to compute the effective URI for the service bindings.
Are we on the same page?
Thanks,
Raymond
----- Original Message ----- From: "Simon Laws"
<[EMAIL PROTECTED]>
To: <[email protected]>
Sent: Wednesday, June 06, 2007 3:11 PM
Subject: Re: Servlet path change?
Raymond, if you think CompositeBuilder is the right place to do this
then I
have to bow to your better judgement.
The binding base URLs should be stored in a topology model (as in the
SCA
Binding and Distribution thread). So if you are going to make this
change it
would be good to instigate enough of the topology model to to support
your
change. Happy to help with this as I want to start moving the beginnings
of
the distributed implementation into the trunck.
Regardless of the format this actually arrives in I guess we need at
least
the following to get your change to work.
domain
runtime
name
binding
name
scheme
name
baseuri
Regards
Simon
I'd like to keep this modular and continue to have a clear separation of
concerns between assembly, interfaces, databindings, and now... the
topology aspects.
So I suggest to put the model describing the topology of an SCA domain and
the builders/processors/etc that handle it in a new module, separate from
the assembly module, which is really specialized in the domain logical
composition.
In that modular architecture, CompositeBuilder will continue to know only
about logical composition, and we can have a new WhateverBuilder in that
new topology module to handle the building of the topology model and the
determination of the base binding URIs.
--
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]
