On 6/25/11 14:16 , Niclas Hedhman wrote:
On Sat, Jun 25, 2011 at 2:09 PM, Rickard Öberg<[email protected]> wrote:
If you want that to be the whole definition of a Value, it won't work. It
still needs to be a mixin with an interface.
Well, I am coming from a 'requirements' (really, really NICE to have)
that we should be able to consume POJOs as values and entities.
Now, HOW that can be satisfied, if at all, is of course another story.
I would expect a great deal of bytecode magic for it to happen, but
right now I am just raising the Attention that this could be a nice
road into legacy systems...
I see your point. Well, if a class can be a composite, it would then mean:
* Subclass has to be generated
* Constraints would work
* Typed concerns and sideeffects only work for implemented interfaces
* Generic concerns and sideeffects work without issues
* Private mixins should be possible
Something like that would be extremely useful for TransientComposites
anyway, since they typically only have one mixin anyway.
Definitely worth looking into.
/Rickard
_______________________________________________
qi4j-dev mailing list
[email protected]
http://lists.ops4j.org/mailman/listinfo/qi4j-dev
