On Sun, Jun 8, 2008 at 8:45 AM, ant elder <[EMAIL PROTECTED]> wrote: > On Sat, Jun 7, 2008 at 12:46 PM, Simon Laws <[EMAIL PROTECTED]> > wrote: > > <snip> > > I've created an itest (late-reference-resolution) to show how late > > resolution could be done using endpoint resolvers. > > > > > In the itest BindingScaEndpointResolverImpl it says "I can cheat here > because..." could you say a little about how a "real" use of this could > work? And what do you think about having some code somewhere - in an itest > or module somwhere - which demonstrates that? I'd be happy to help write > that, I'm asking as in runtime-tomcat i need to do the same thing but > haven't been able to figure out how its intended to be done for real. > > ...ant >
The real use of this involves writing more code. The late binding feature is one way of catering for scenarios where, for example, the domain is not completely configured when the first composite is run. To make this work a registry needs to provide the information required for references to locate services at runtime, i.e. service name, contract, intents/policies and target URL. The EnpointResolver provides a plug point where runtime or binding specific code can be put to do this reference resolution. I haven't done any work on the service side. I think the domain or the runtime can collate service information generically without it being done at a service or binding level. Time will tell. Runtime-tomcat is an example of where this kind of approach can be useful. Here the driving requirement is to support a contribution deployment step where a war is simply dropped into tomcat/webapps. The normal semantics of this are that the webapp is immediately available. It could be argued that this is a specious scenario because even if a web app is available from the Tomcat point of view SCA components in the war won't operate correctly until all references are satisfied. However I think this is a common enough deployment scenario that we should investigate it. Regards Simon
