Niclas Hedhman a écrit :
Another thing; Activatable starts showing up in new places, for a
different purpose. That is probably quite unfortunate if we are going
to try and remove it from client code later.
Actually, the Activatable interface is quite usefull as a type definition
to easily add the activate() and passivate() methods and as a type selector.
With a simple helper the code impact could be reduced to adding the
following
annotation on concerned services:
@Activators( ActivatableServiceActivator.class )
This would allows us to remove the Activatable handling from the runtime but
still provide the Activatable interface alongside the helper shown above.
WDYT ?
_______________________________________________
qi4j-dev mailing list
[email protected]
http://lists.ops4j.org/mailman/listinfo/qi4j-dev
