[jsr294-modularity-eg] Runtime model

Andreas Sterbenz Andreas.Sterbenz at Sun.COM
Mon Jul 16 19:52:57 EDT 2007


Bryan Atsatt wrote:
> Glyn and I both agreed that the use case is limiting external access to 
> legacy classes in a module. Supporting this at runtime allows the 
> unmodified legacy classes to continue to run in pre-Java 7 environments, 
> thus simplifying build/support/distribution.

By "legacy classes in a module", do you mean JSR 277 module? Since JSR 277 
is currently also targeted for JDK 7, a JSR 277 module will not run on JDK 
6 regardless of superpackages (unless potentially as a plain JAR file, 
which would largely defeat the purpose of making it a module).

Or which other deployment mechanism are you thinking of?

Andreas.


More information about the jsr294-modularity-eg mailing list