On 7/3/06, Jim Marino <[EMAIL PROTECTED]> wrote:
In order to do this, I had to change the signature of of things like DeployerImpl to pass the parent composite through. Perhaps a better long-term solution will be to add a method to DeploymentContext that will return the parent composite, as that is also passed through. To do this, we may need to refactor how deployment evaluates nested composites as I believe it passes a single deployment context through as child composites are processed.
Yes it does and as you've found I think this will be limiting. We already need to create a new context as we add child classloaders in so I think the best option would be to add the parent to each context as we recurse down. I want to make sure we have information about the component actually being deployed - I think that's there with the module scope. Cheers -- Jeremy --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
