Niclas Hedhman wrote:
Since this approach gives exactly 1 extra subclass per Fragment type, independently of how many times it is used in Composites, I think we have a 'reasonable' overhead.
Ok, good.
It will however change the claim of "No Magic under the Hood", and definitely stop corner use-cases such as Android and potentially even Google AppEngine and other future cloudservices, which most likely will block bytecode manipulation.
Yes, that is probably true.
So, I am +1 to making this enhancement now, and that we in the longer term try to look for a solution where we can break this functionality out to compile time so that we can manage cloud services, Android and other restricted environments (Applets?).
For applets, you could always sign them. That's what I have done before, and am doing now with JavaWebStart clients. Since I'm guessing Qi4j will mostly be used for domain-apps anyway, you will want to have them signed.
/Rickard _______________________________________________ qi4j-dev mailing list [email protected] http://lists.ops4j.org/mailman/listinfo/qi4j-dev
