Whoops, .jsp files are not candidates for private resources, since the
*container* must have access to them. But I stand by the gif/html/xml
comment :^).
Another candidate is property files (thanks to Stephen McConnell for
reminding me), when used as default configuration.
Bryan Atsatt wrote:
Hi Bryan,
I would like to get closures on a few open issues first, so my responses
will be limited to those threads rather than all the new threads that
have been started recently.
Bryan Atsatt wrote:
Hi Stanley,
Sorry if I'm not being clear. Let me try to summarize:
- I *do* want 277 to
Some feedback from an observer which may help:
Bryan misses the need for extender model to load internal impl classes
ala
Bundle.loadClass in OSGi.
You do not want to have to export the service impl class from a module.
You want to hide the class from others' casual loading. However an
I don't think I'm missing anything, just looking at it from perhaps a
different perspective :^)
First, 294 will determine accessibility for non-exported classes. The
assumption at the moment is that they will not be accessible to *any*
class outside of the module.
I do understand the value of a
I've been assuming that Module private resources should not be visible
to *any* class outside of the module. Including ResourceBundle, or any
other existing framework classes that do resource lookups (e.g.
ServiceLoader, JSF, etc). If resources need to be visible to these
existing classes, they
Hey Stanley,
Sorry to be generating so much traffic while you're traveling! I'm not
in any rush here, so feel free to take your time responding...
Stanley M. Ho wrote:
Hi Bryan,
A module can use the ResourceBundle API to retrieve resources from other
resource modules, but it can also use the
