Gang,
IF this "multi-type composites" now seems like a good idea, there are
things that will need more work. The immediate things I see are;
1. Now "composite type" is an "Iterable<Class>" because it is also
shared across non-composite types that are supported, such
ImportedService and Object. I think it is strange that we have for 4
years been talking about "CompositeType" as a concept and it doesn't
exist in our code. I plan to introduce such interface and I think a
similar NativeType is needed as well for the other two. A lot of code
should be collapsed into the implementation of CompositeType, such as
assignability checks, creation of an instance, pretty much like
java.lang.Class.
2. The ModuleAssembly interface needs review, and the assembly DSL
(if we could call it that) should probably be modified;
module.service().ofTypes(Abc.class, Def.class).withMixins( XyzMixin.class );
module.entity().ofTypes(Abc.class, Def.class).withMixins( XyzMixin.class );
is one possibility. That will lead to a lot more "lines of code", and
I am open to suggestions.
3. Paul raised a lot of questions around serialization and
EntityTypes. I am sure this will need to be looked at in great detail,
but better delay that until 1. above is done.
Anything else in the near term?
Cheers
--
Niclas Hedhman, Software Developer
http://www.qi4j.org - New Energy for Java
I live here; http://tinyurl.com/3xugrbk
I work here; http://tinyurl.com/6a2pl4j
I relax here; http://tinyurl.com/2cgsug
_______________________________________________
qi4j-dev mailing list
[email protected]
http://lists.ops4j.org/mailman/listinfo/qi4j-dev
