Niclas Hedhman a écrit :
On Mon, Oct 22, 2012 at 8:05 PM, Paul Merlin<[email protected]> wrote:
Asking for an injection like this ;
@This Configuration<Enabled> config;
will trigger an Entity lookup using the enclosing service's identity.
I cannot see how it could get the wrong configuration entity.
That is not what he is saying;
I think it is like this;
All service configurations are having Enabled as a supertype.
There is no default initialization for any of the service configuration.
In the assembly, a forMixin(Enabled.class) is used to set the default
value to TRUE.
But on occasions, Enabled is not set to its default value.
Oh ok :)
My bad.
forMixin() operates on the mixin type, not the composite type. So, if
many composites are using the same mixin type, there would only be a
single default value. The question is then; Is it possible that
StreamFlow has another forMixin() of a type where Enabled is involved
(perhaps not directly) which could cause the defaults to be
inadvertently changed.
Understood.
It is a complex issue, and it would be great with a testcase, but I
doubt that can be produced before we guess what is happening.
Sure.
_______________________________________________
qi4j-dev mailing list
[email protected]
http://lists.ops4j.org/mailman/listinfo/qi4j-dev
