On 7/6/07, Mike Edwards <[EMAIL PROTECTED]> wrote:
Huang, I assume that by "reference" here, you mean a service reference? If that is so, it should work. If you mean that composite A has a component which uses composite B as an implementation and that composite B has a component which uses composite A as an implementation - then this IS an illegal cyclical usage and should generate an error. Yours, Mike. Huang Kai wrote: > When CompositeA has reference to CompositeB while CompositeB also has reference back to CompositeA, CompositeBuilderImpl.build(composite) seems went into endless loop. > I'm not very sure whether it's a bug or this kind of reference is illegal? --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED] Mike
For clarification. In the first case is the assumption that the application will ensure that messages do not pass round the loop forever. Simon
