I 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 . I think this use case is fairly common, eg. [Employee] has a property refer to [Company] and [Company] has a property refer to it's [Employee]s. And when these two java components are in different composites, I'll have to define mutual referenced composite files above.
----- Original Message ----- From: "Mike Edwards" <[EMAIL PROTECTED]> To: <[email protected]> Sent: Monday, July 09, 2007 4:37 PM Subject: Re: StackOverflowException when mutual reference exist > Huang, > > Can you clarify what you mean please? > > What configuration of composites are you using? > > Yours, Mike. > > Huang Kai wrote: >> I'm in the case 2. >> :( >> It's error-prone >> >> ----- Original Message ----- >> From: "Simon Laws" <[EMAIL PROTECTED]> >> To: <[email protected]> >> Sent: Friday, July 06, 2007 11:11 PM >> Subject: Re: StackOverflowException when mutual reference exist >> >> >>> 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 >>> > > --------------------------------------------------------------------- > To unsubscribe, e-mail: [EMAIL PROTECTED] > For additional commands, e-mail: [EMAIL PROTECTED] >
