Hi, I was planning on playing around with the current composite impl capabilities..... with the following questions in mind:
If anyone knows the "short answer" to any of these questions I'd appreciate hearing what you had to say; it would give me a better starting point... ======================================================================================= Q1.) How is a binding on a service in a nested composite handled? That is, suppose I deploy top-level composite Z1 which contains component C1, and that C1 is implemented by composite Z2. Could I put a WS binding on a composite-level service S of Z2? Would I need to surface S to the Z1 composite and put a WS binding on the service surfaced to the Z1-level? I'd assume I would be able to override the URL the service can be invoked at (or some right-hand portion of the URL ) at the Z1 level. Q2.) What packaging formats are supported for packaging including and implementing composites within a top-level composite? Can included and implementing composites be packaged as jars within the top-level archive (JAR or WAR), in which case you'd point from the top-level SCDL (e.g. 'default.scdl') to a scdlLocation like: z2.jar#z2.scdl ? Or must the entire archive be "flattened out", like, the example JAR in samples\sca\inner.composite? Is this strictly a question of what the ClassLoaders in question have on their paths? (in which case the CompositeLoader.load() method should show the answer to my question) Or are there other Tuscany reasons why the options are limited? Could I point to SCDL anywhere in my HFS if I put it on my classpath? (And how would I?) ======================================================================================= Thanks, Scott
