Jochen Theodorou wrote: > but this works only for classes that you can change. If it is a class > coming from some parent loader, that you have no control over, then it > won't work.. or do I see that wrong? > > Maybe the typical usage scenario is different here with Groovy
No, this works for all classes, but you have to subvert reflection and have appropriate security allowances. I'm actually modifying state inside the java.lang.Class objects themselves. Like I said, it's a hack, but it saves you associating state with Class objects in an external structure. If the java.lang.Class object goes away, so does your data. - Charlie --~--~---------~--~----~------------~-------~--~----~ You received this message because you are subscribed to the Google Groups "JVM Languages" group. To post to this group, send email to [email protected] To unsubscribe from this group, send email to [email protected] For more options, visit this group at http://groups.google.com/group/jvm-languages?hl=en -~----------~----~----~----~------~----~------~--~---
