[jsr294-modularity-eg] JSR 294 expert group draft
bryan.atsatt at oracle.com
Tue Oct 23 13:37:51 EDT 2007
There was no discussion of this issue, to my knowledge.
And I don't see it a as a feature, but an issue: runtime class
generation is a common and seemingly growing usage pattern. Proxies and
other such generated classes should be able to participate as first
class citizens in the superpackage world; I believe that this means
java.lang.reflect.Superpackage instances must be _mutable_ , at least to
support additions to the member and export lists.
Andreas Sterbenz wrote:
> [All - there are still problems with the EG mailing list. I hope that
> will be resolved soon, but until that happens please send mail to the
> list and also CC all the EG members, e.g. by doing a reply-all to this
> message. Thanks.]
> Bryan Atsatt wrote:
>> I haven't yet had time to review these, but... Does this draft
>> address the runtime class generation issue?
> there was no consensus on this feature in the EG and there were some
> unresolved questions, so it is not included in this draft of the spec.
> We can of course list it as on open issue. It is also not quite clear
> to me which changes - if any - to the JLS and JVMS would have to be made.
More information about the jsr294-modularity-eg