[jsr294-modularity-eg] Why Require is Considered Harmful
Mina R Waheeb
syncer at gmail.com
Sat Mar 7 05:05:16 EST 2009
The module Require problem is a result of the VM execution mechanism and
the idea behind the classes lazy loading. The classloaders use package plus
classname as URI for locating the class byte code when needed, By using
load-on-request methodology first class loaded will define the module, so
the question appears here How can we locate a module?
But before go so far, why we need require module? And the requirement
already enforced by the class imports. The only case I see applied here to
give a custom classloader the ability to load the required module from
none-classpath repository. More configuration, extra
requirement and constrains. Very high cost for already solved problem. even
if implement any platform like eclipse, netbeans or ejb system will require
extra configuration than module dependency, you will also put a config file
in each module so it will not be so hard for the custom classloader override
defineModule method and parser platform specific config file and start load
And as you said "Realize that once you get it wrong in a specification, you
can never get rid of it"
Mina R Waheeb
-------------- next part --------------
An HTML attachment was scrubbed...
More information about the jsr294-modularity-observer