Yes, that's the text that was bothering me. It isn't very well worded.
Anyway I think we're ok.
On Fri, Aug 12, 2011 at 11:19 AM, Simon Laws simonsl...@googlemail.comwrote:
On Fri, Aug 12, 2011 at 1:10 PM, Greg Dritschler
greg.dritsch...@gmail.com wrote:
I thought this over again, and based
I thought this over again, and based on everything Mike has said, I think my
proposed fix is wrong. pushDownEndpointReferences() is adding targets from
a component reference to its leaf component reference. This should always
be an add operation, never a replace. That's why ASM_5023 is now
On Fri, Aug 12, 2011 at 1:10 PM, Greg Dritschler
greg.dritsch...@gmail.com wrote:
I thought this over again, and based on everything Mike has said, I think my
proposed fix is wrong. pushDownEndpointReferences() is adding targets from
a component reference to its leaf component reference. This
On Fri, Aug 5, 2011 at 10:49 PM, Greg Dritschler
greg.dritsch...@gmail.com wrote:
Thanks Mike, this helps a lot.
I think the description of nonOverridable needs to explicitly say that it
applies to all of the methods described in 4.3.1. It also needs to say that
it controls not only how
On Mon, Aug 8, 2011 at 2:08 PM, Simon Laws simonsl...@googlemail.com wrote:
On Fri, Aug 5, 2011 at 10:49 PM, Greg Dritschler
greg.dritsch...@gmail.com wrote:
Thanks Mike, this helps a lot.
I think the description of nonOverridable needs to explicitly say that it
applies to all of the methods
On Thu, Aug 4, 2011 at 4:44 PM, Greg Dritschler
greg.dritsch...@gmail.com wrote:
Thanks Mike.
5018 is close to my test. In 5018, the inner composite (TestComposite10)
has the binding on the COMPOSITE reference. In my test, the inner composite
has the binding on the COMPONENT reference, and
Simon,
You seem to be saying there's an equivalence between binding.sca @uri and
reference target in terms of promotion behavior. I cannot find anything in
the spec that supports that.
Here is the description of nonOverridable:
876 nonOverridable : boolean (0..1) - a boolean value, false by
Greg,
I'll try to address this with some inline replies, but I get the feeling that maybe a conf call will
be needed to interactively work on your concerns.
Yours, Mike.
On 05/08/2011 16:12, Greg Dritschler wrote:
Simon,
You seem to be saying there's an equivalence between binding.sca
On Fri, Aug 5, 2011 at 4:53 PM, Mike Edwards
mike.edwards.inglen...@gmail.com wrote:
Greg,
I'll try to address this with some inline replies, but I get the feeling
that maybe a conf call will be needed to interactively work on your
concerns.
Yours, Mike.
On 05/08/2011 16:12, Greg
Thanks Mike, this helps a lot.
I think the description of nonOverridable needs to explicitly say that it
applies to all of the methods described in 4.3.1. It also needs to say that
it controls not only how targets are handled between the composite ref and
its promoted component ref, but also
On Wed, Aug 3, 2011 at 8:37 PM, Greg Dritschler
greg.dritsch...@gmail.com wrote:
I have the following composites:
Composite A has a component reference myService with binding.sca uri=X.
The reference is promoted.
Composite B has a component that uses A as its implementation. It redefines
On 04/08/2011 10:27, Simon Laws wrote:
On Wed, Aug 3, 2011 at 8:37 PM, Greg Dritschler
greg.dritsch...@gmail.com wrote:
I have the following composites:
Composite A has a component reference myService with binding.sca uri=X.
The reference is promoted.
Composite B has a component that uses A
From the assembly spec on component references:
900 binding : Binding (0..n) - A reference element has zero or more binding
elements as children. If no
901 binding elements are specified for the reference, then the bindings
specified for the equivalent
902 reference in the componentType of the
On Thu, Aug 4, 2011 at 2:27 PM, Greg Dritschler
greg.dritsch...@gmail.com wrote:
From the assembly spec on component references:
900 binding : Binding (0..n) - A reference element has zero or more binding
elements as children. If no
901 binding elements are specified for the reference, then
On 04/08/2011 14:27, Greg Dritschler wrote:
From the assembly spec on component references:
900 binding : Binding (0..n) - A reference element has zero or more binding
elements as children. If no
901 binding elements are specified for the reference, then the bindings
specified for the
Thanks Mike.
5018 is close to my test. In 5018, the inner composite (TestComposite10)
has the binding on the COMPOSITE reference. In my test, the inner composite
has the binding on the COMPONENT reference, and the COMPOSITE reference
promotes that reference without specifying any bindings (so
I have the following composites:
Composite A has a component reference myService with binding.sca uri=X.
The reference is promoted.
Composite B has a component that uses A as its implementation. It redefines
reference myService and specifies binding.sca uri=Y.
I get the error
[ASM50022] Too
17 matches
Mail list logo
