"alesj" wrote :
| This is an old discussion, that as I see it now, never got properly resolved:
Isn't there a better solution for this problem? I know can get rid of the overhead by
mapping the module to the exported classes. But this means relying on implementation
detail I shouldn't even be aware of.
"Ales" wrote :
| How else would a call to
ClassLoader::getResource("META-INF/some-config.xml") work? ;-)
But if somebody puts SomeClass.class in META-INF, the class loader will be able of loading
META-INF.SomeClass. I know this scenario is totallly awkward and should never happen, but
aren't we supposed to cover corner cases?
View the original post :
Reply to the post :