Hi, Yeah, the idea was to start from something easy and non-critical. But it seems like PropertiesMixin will be considered useless, so any suggestion on what would be more suitable? About the constraint, is the constraint just able to intercept a method call, or we can intercept object(composite) creation, or we can even use constraint to check a program(types) static structure via reflection?
2008/11/25 Niclas Hedhman <[EMAIL PROTECTED]> > On Tue, Nov 25, 2008 at 12:37 PM, tao wen <[EMAIL PROTECTED]> wrote: > > Hi, > > > > how about my another question, the constraint on how a composite looks > like, > > such as if you have a getter and setter for same property, they should > have > > same type. I don't know if current "constraint" support checking a static > > type structure, to enforce some design decision, when addComposite to a > > assembly? > > I am on the road and don't have the code in front of me right now. > IIRC, the Iterator support was together with add/remove support for > collections. But this code used to be the "mainstream", but after the > introduction of Property/Association/ManyAssociation about a year or > more ago, its existence has faded to a library of Javabean support, > which I have not worked on for a while. The good part of that is that > you messing around is not critical and you have fairly free hands to > evolve the library. Keep the discussion going. > > > Cheers > Niclas > > _______________________________________________ > qi4j-dev mailing list > [email protected] > http://lists.ops4j.org/mailman/listinfo/qi4j-dev >
_______________________________________________ qi4j-dev mailing list [email protected] http://lists.ops4j.org/mailman/listinfo/qi4j-dev
