On 5/30/11 12:16 , Paul Merlin wrote:
It's great to see application assembly getting such improvements. Actually it can be painfull when you have a lot of fragments. I will use this and it will reduce assembly code in my applications.
That's what I found as well. We had 30+ registrations that could be replaced with "register all *View classes as objects", for example.
I wonder what is the scope of the basic getClasses() scanner. Do it return all classes in the same package as the "starting point" class ?
Same package, and all underlying packages. So if you want you can point it to a class very high up in the hierarchy and base the iteration on name filtering. Or, specify a specific package. Both ways are possible. You could also combine it with annotation checks, or supertype checks (e.g. "all classes that extend ValueComposite should be registered as values").
I'm offline now for a couple of days due to travel, but will then check in all of this, with samples, later in the week.
/Rickard _______________________________________________ qi4j-dev mailing list [email protected] http://lists.ops4j.org/mailman/listinfo/qi4j-dev
