Huang,
Huang Kai wrote:
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
: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
: 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
I'm in the case 2.
:(
It's error-prone
- Original Message -
From: Simon Laws [EMAIL PROTECTED]
To: tuscany-dev@ws.apache.org
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
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
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
when mutual reference exist
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
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?
