On Tue, Nov 25, 2008 at 2:15 PM, tao wen <[EMAIL PROTECTED]> wrote: > 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?
The lib-beans is all about creating support to interact with JavaBeans compliant (and perhaps less compliant one) code, that we find in existing subsystems, external/remote services and so forth. For this purpose, the PropertiesMixin will probably still have a place. > 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? Constraints (at the moment) only checks method arguments. We have discussed to also do it for returned values. I suspect that Constraints can be placed on Constructors, although I have not checked that this is true. It should exist, and if it doesn't I would consider it a bug or "missed feature". I don't see what value constraints would have to check for static structure. Please elaborate with a use-case if you want to push this idea further. Cheers Niclas _______________________________________________ qi4j-dev mailing list [email protected] http://lists.ops4j.org/mailman/listinfo/qi4j-dev
