Hi Wade,
Wade Chandler wrote:
--- On Sat, 5/31/08, Mark Brouwer <[EMAIL PROTECTED]> wrote:
From: Mark Brouwer <[EMAIL PROTECTED]>
Subject: Re: Change to net.jini API
To: [email protected]
Date: Saturday, May 31, 2008, 6:32 AM
Mark Brouwer wrote:
All,
Attached you will find a patch for RIVER-147 and
RIVER-265. Note that
RIVER-147 represent a new protected method on a class
in the net.jini
namespace. To me this a public API change in the
net.jini namespace so
please all have a good look at it and tell what you
think of it.
The enhancements represent the minimal specification
of what is referred
to in RIVER-147, but the enhancements represent all
that I needed to
support codebase evolution for Seven.
RIVER-265 represents an internal change that is a
direct consequence of
the functionality provided by RIVER-147.
Did anyone have had a look at this change, I don't want
to commit this
given the fact it is a change in the net.jini API which is
rather hard
to remove if it turns out it ain't that smart after
all.
I meant to point out that I didn't get:
protected boolean isClassDefinedInClassLoader(String codebase,
ClassLoader loader)
If there is a better method name I'm all for it, I think the method
level javadoc gives a better description of what it does and the name
was the best at a certain evening I could come up with.
as it seems per the method name the parameter codebase would be
className. Is that what it was supposed to be, or is the intended use?
What is passed in is really the same argument (codebase) as what is
passed in at the call below:
PreferredClassProvider.loadClass(String codebase,
String name,
ClassLoader defaultLoader)
So it is really the codebase as found in a marshalled stream e.g.
--
Mark
