On Fri, Apr 25, 2008 at 1:22 PM, <[EMAIL PROTECTED]> wrote: > Hi Simon, > > thanks for your answer. I remember you wrote a similar answer when I > asked about load balancing and failover. > I'll have to get my hands on this workspace stuff, soon. > > It would be great if you guys could provide a little more documentation > on the website. Everything I have read so far was not self-explanatory > (at least not to me). So this will be of interest to more people than > me, I guess. > > Thanks for now. > > Bye, > Daniel > > > Hi > > > > It will work when reference and service are in different > > composites if you use the domain workspace to process the > > composited prior to then being deployed to nodes. > > > > What happens is that you have the workspace-admin app running > > and you add your contributions (containing the composites) to > > the workspace. You also provide configuration which tells the > > workspace where the nodes are that are going to run the > > composites and which composites they will run. Based on this > > information the workspace make various (2 in the case of 2 > > composite to > > run) atom feeds available. Each can be read by a node to > > determine which composite to run and which contributions must > > be retrieved in order to provide the artifacts required by > > the composite. > > > > As you can probably imagine the workspace processes all the > > relationships between all composite components and provides a > > fully configured composite to each node, i.e. all of the > > binding URIs are filled out based on the target relationships > > specified in the composite files. So it's basically a > > pre-processing step. You can simulate the effect by manually > > adding the full uri to the reference binding.ws in your case. > > > > The calculator-distributed sample is a simple example of the > > use of the workspace. You can fire up the workspace and play > > with the gui or look at the 3 xml files in the top directory > > of that sample which the workspace relies on for configuration. > > > > Regards > > > > Simon > > >
Yeah, I agree. The docs in this are a already thin and haven't kept up with the changing code. We do need to fix that. Regards Simon
