I think I have managed to find the problem. The code for diving down through the composites to resolve all the references had been commented out in the wireCompositeReferences() method of CompositeWireBuilder.
I've uncommented out the code and it now correctly resolves multiple level nested references. With this change, it now mirrors the behaviour that is implemented for Composite Services which also dives down through the services of each Composite. I'm going to do some more testing and then commit the fix. Mark -----Original Message----- From: Mark Combellack [mailto:[EMAIL PROTECTED] Sent: 04 February 2008 13:24 To: [email protected] Subject: Any hints as to where to look to fix problem with nested composites? Hi, I've just raised a bug about nesting an implemtation.composite within another implementation.composite - see https://issues.apache.org/jira/browse/TUSCANY-2027 I'm having problems working out how to fix the issue. I think it is an assembly problem as the target of the Reference does not have a Contract. Does anyone have any suggestions of where I should be looking to try to fix this issue? Thanks for your help, Mark --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
