On Fri, May 15, 2009 at 11:16 AM, Simon Laws <[email protected]> wrote:
> Having been through this experiment it feels more complicated than I'd > hoped and I'm wondering if there is an easier way to make this > scenario work. > > The first thought that comes to mind is treating OASIS and OSOA > composites completely separately in the domain from a processing point > of view but get them to interact by instigating a service registry > mechanism. We need a registry of some sort to make SCAClient and late > binding work. I don't think it is so such a leap then to exploit this > in the 1.x/2.x scenario for cross domain endpoint resolution. We would > have to have the domain access 1.x and 2.x code bases independently > (OSGI?) based on what type of composite is found. We would also need > to fix the SCA binding to allow it to look up service in a registry > again. I think that's on the cards for 2.x anyhow but it would be a > change in 1.x > +1 for looking at a service registry approach as it seems to have many benefits including helping with more dynamic domain operation. > There are problems inherent in this approach though,for example, how > to deal with policy which are supposed to be domain wide. > Policy may not be such a problem if we accept a restriction that domain wide policy would only apply to nodes at the same sca version as the policy? ...ant
