[jsr294-modularity-eg] Runtime model

[Andreas Sterbenz]

Glyn Normington wrote:
> 
> Further to my comments below, I'd like us to explore why loading a 
> legacy class into a superpackage would be deemed to be changing, rather 
> than compatibly extending, its semantics?

Sure. I think we should start by examining the use cases. Some of the 
questions in my mind are:

When is it is necessary to dynamically draft legacy classes into the 
superpackage?

Why are approaches that expose classes that are a member of a superpackage 
and legacy classes as one "component" (module, bundle, etc.) not 
sufficient? They can coexist just fine.

Another approach is static class file rewriting. When is that not sufficient?

Andreas.