On Fri, May 9, 2008 at 9:51 AM, Simon Laws <[EMAIL PROTECTED]> wrote:
> > > On Fri, May 9, 2008 at 7:23 AM, ant elder <[EMAIL PROTECTED]> wrote: > >> On Thu, May 8, 2008 at 9:40 PM, Simon Laws <[EMAIL PROTECTED]> >> wrote: >> >> <snip> >> >> If you are up for adding a bit of dynamic behaviour we could extend the >> > domain manager to provide a feed of the services that are currently >> > available in the domain and then use this in conjunction with the >> dynamic >> > binding stuff I'm currently working on to allow references to be >> resolved >> > at >> > point of time after composite start. Quite a bit of work there though. >> > >> > >> That approach sounds interesting, though I don't need a feed as this is in >> the same JVM so just a service to call to get the available services. The >> feed could be from another app that exposes the service to external >> clients. >> >> >> Could you say a bit more about what is the dynamic binding stuff you're >> currently working on? >> >> ...ant >> > > Sure, I just posted some more thoughts here [1] > > In summary, some reference targets may not be resolved at build time if the > domain is not completely configured at that point. I recently put a change > in to create an SCA binding to represent unresolved targets the > understanding being that the SCA Binding could perform some magic at a later > stage to try again to locate the target service. > > I'm now proposing to change the use of a sca binding in this case for a > special binding, called Enpoint, to provide this feature. The thought being > that in the future we will make some breaking changes where Endpoint becomes > a first class citizen in the model. This is motivated by a few things. > Firstly I want to make the code that extracts target names from model > binding URIs more generic, I now think using the SCA binding in this role is > confusing and I also want to reuse as much of the builder target service > matching code as possible in both early and late binding cases. > > Hope that helps > > That does help, i don't fully understand the details but it sounds about perfect for whats needed in this Tomcat scenario. With that in place it should be possible to have the domain start up "empty" without having to know about any nodes, then new nodes be created or registered with the domain and any cross node endpoints only get resolved the first time they're invoked. Does that sound right? How will the endpoint binding do the actual resolution - by asking the domain? ...ant
