If we are going to move away from extending Composite meta types, then
there is an interesting observation;
module.services( Executor.class ).withMixins(
ThreadPoolExecutor.class ).withConcerns( ExecutorProgressConcern.class
);
or
module.values( Map.class ).withMixins( HashMap.class
).withConcerns( PutCheckConcern.class );
and so on, that would actually work??
If so, what are the positive consequences in terms of integration
across the open source world?
I don't have the answer, just a GutFeeling(tm) that this could be
really, really game changing...
One thing that I can think of is around enabling 'soft introduction'
of Qi4j into existing apps. A really low impact usage;
Module module = new SingletonQi4jApplication() { ..implement
assemble() }.module();
Map aopMap = module.newValue( Map.class );
module.service( Executor.class ).execute( new Runnable() { .... } );
And perhaps even provide a suitable Spring application context
embedded in Qi4j Core so the above Module is available as a bean if
you put it into Spring.
Anybody have any thoughts?
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/24svnvk
I relax here; http://tinyurl.com/2cgsug
_______________________________________________
qi4j-dev mailing list
[email protected]
http://lists.ops4j.org/mailman/listinfo/qi4j-dev
