Michael Hunger wrote:
> When doing the test fixing I came around a bug (or perhaps not) that
> manifests itself with Rickards new implementation.
>
> You quite often find a construct like this.
>
> public interface HelloWorldConfiguration extends EntityComposite
> {
> Property<String> phrase();
>
> Property<String> name();
> }
>
> The problem at resolution time manifests itself in the former case that the
> Service that uses the configuration.
>
> public static class HelloWorldMixin
> implements HelloWorld, Activatable
> {
> @This
> Configuration<HelloWorldConfiguration> config;
> ....
> }
>
> So, because of the EntityComposite that is already implemented by the
> HWConfiguration interface the Service also must
> implement all Interfaces or have at least mixins for the interfaces needed by
> EntityComposite.
> (The problem here being Lifecycle).
The bug was that with this injection:
@This X<Y>
Y was being implemented as a this-interface, whereas it should have been
X. This has been fixed now.
/Rickard
_______________________________________________
qi4j-dev mailing list
[email protected]
http://lists.ops4j.org/mailman/listinfo/qi4j-dev
