probably due to my j2ee experiences... I was wondering how / if the runtime would react to different versions of the same component/composite, but I'm sure we have some for of classloader isolation that would handle this... just use to the j2ee way and had assumed (due to launcher's command line arguments) that composites needed to be packaged (in a jar or similar) so that they could be contributed to the domain - obviously got that wrong :) Cheers, Dan
On 05/03/07, Jeremy Boynes <[EMAIL PROTECTED]> wrote:
On Mar 5, 2007, at 2:10 PM, Dan Murphy wrote: >> >> There may be some confusion here over "deploy." In SCA you don't >> "deploy" applications in the traditional sense - you contribute >> implementations to a domain and then assemble component hierarchies >> from them. > > > Interesting, I appreciated that there was no deploy (ala J2EE) but had > assumed that composites were isolated. I guess I misinterpreted the > reasons > behind Sebastien's separation to run under different vms... Not sure what you mean by "isolated" but composites are logical groupings (er, compositions :-) ) of components that are orthogonal to the physical topology. Unless the composite is specifically marked "local" or unless connected by local references, the components in a single composite could quite easily be running in different physical runtimes. Supporting this core architectural tenet in a federated world is one of the changes going on in trunk atm. -- Jeremy --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
