Adrian [EMAIL PROTECTED] wrote on 25/05/2007 12:44:54:
On Thu, 2007-05-24 at 11:00 +0100, Glyn Normington wrote:
A better approach would be for the Java 7 platform to provide first
class support for JSR 291. This boils down to standardising the
experimental class loader deadlock fix ([1])
Responses inline, and a few clarifications here (I was a bit tired when
I finished this last night :^)...
The main point I was trying to make is that resolution must occur within
a specific context, but I don't think my example APIs showed that well.
I was assuming that ImportResolver had 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
Hi,
Glyn Normington wrote:
*Bryan Atsatt [EMAIL PROTECTED]* wrote on 30/05/2007 07:57:59:
...
So the open issue is the richness of the import language: must we
support only lowest-common-denominator, or can we do better without
over-complicating the design?
I for one would like to be
Hi Richard,
Richard S. Hall wrote:
Hey Stanley,
...
To me, this sounds like what we call the extender model for the OSGi
framework. The way it works is that bundles that want to participate in
certain scenarios simply include some metadata inside of themselves,
then some infrastructure can
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
