On Tuesday 15 April 2008 16:50, Rickard Öberg wrote:
> Does this sounds like a good idea?
Sounds ok to me.
> If yes, what methods from ModuleInstance down to ModuleModel should be
> included?
Priority 1; // Definately
=========================
ImmutableProperty<Boolean> activated();
ImmutableProperty<String> name();
ImmutableProperty<Layer> layer();
Priority 2; // Maybe
==========================
Module moduleForComposite( Class<? extends Composite> compositetype );
Module moduleForMixinType( Class<?> mixintype );
Module moduleForObject( Class<?> objecttype );
boolean isPublic( Class<?> compositeOrObject );
Class<? extends Composite> lookupComposite( Class<?> mixintype );
Priority 3; // Maybe not.
==========================
ServiceReference<T> lookupService( Class<T> serviceType );
Iterable<ServiceReference<T>> lookupServices( Class<T> serviceType );
void activate();
void passivate();
And something like;
public interface Layer
{
ImmutableProperty<String> name();
Iterable<Layer> usesLayers();
Iterable<Layer> usedByLayers();
Iterable<Module> modules();
boolean isPublic( Class<?> compositeOrObject );
}
> Also, if yes, then support for "@Structure ModuleBinding" will be
> replaced with "@Structure Module".
Definately.
Cheers
--
Niclas Hedhman, Software Developer
I live here; http://tinyurl.com/2qq9er
I work here; http://tinyurl.com/2ymelc
I relax here; http://tinyurl.com/2cgsug
_______________________________________________
qi4j-dev mailing list
[email protected]
http://lists.ops4j.org/mailman/listinfo/qi4j-dev
