Quoting Rickard Öberg <[email protected]>:
If that's what you want to do, then you could consider using extended composites instead.
<snip>
Is that good enough?
I've considered extended composites too. It's almost good enough - but what happens when someone gets immutable query composite and says uow.remove(iq)? When I give IQ to someone, I don't want it to be removable (well, at least in 99% of cases :) ).
Making IQ's mixin implement Lifecycle and throwing exception in remove() could be one solution, but then the IQ's Lifecycle's overridden remove() will throw exception also in case when entity gets removed via command-role, right?
_______________________________________________ qi4j-dev mailing list [email protected] http://lists.ops4j.org/mailman/listinfo/qi4j-dev
