Mailing-List: contact commons-dev-help@jakarta.apache.org; run by ezmlm
Precedence: bulk
Reply-To: "Jakarta Commons Developers List" <commons-dev@jakarta.apache.org>
Received-SPF: pass (asf.osuosl.org: domain of ggregory@seagullsoftware.com
 designates 12.6.96.2 as permitted sender)
Content-class: urn:content-classes:message
MIME-Version: 1.0
Content-Type: text/plain;
	charset="us-ascii"
Content-Transfer-Encoding: quoted-printable
Subject: RE: [lang] enhanced version of Class.forName
Date: Tue, 6 Sep 2005 12:08:34 -0400
Message-ID: <9E102CCE036F884294D508F6C05A9BD8085A80@ns1017.seagull.nl>
Thread-Topic: [lang] enhanced version of Class.forName
Thread-Index: AcWy9BjuPsYD+loPR7+vpCUBhpFoWgAArrdwAAGK9kA=
From: "Gary Gregory" <ggregory@seagullsoftware.com>
To: "Jakarta Commons Developers List" <commons-dev@jakarta.apache.org>

IMO, you let the underlying JRE API throw the exception.=20

Gary

> -----Original Message-----
> From: James Carman [mailto:james@carmanconsulting.com]
> Sent: Tuesday, September 06, 2005 8:28 AM
> To: 'Jakarta Commons Developers List'
> Subject: RE: [lang] enhanced version of Class.forName
>=20
> Well, what does the [lang] "team" think about this approach (just
letting
> Class.forName() throw the ClassNotFoundException)?  Does this work for
you
> guys?  I have added a patch to issue 36512 which includes code to
> implement
> it this way (my latest patch).  Are there any votes against this
method
> being implemented this way?  If not, do you guys care if I go ahead
and
> commit it (I'll wait a while for votes)?  Since I'm not a "normal"
[lang]
> committer, I don't want to step on anyone's toes.
>=20
>=20
> -----Original Message-----
> From: Emmanuel Bourg [mailto:ebourg@apache.org]
> Sent: Tuesday, September 06, 2005 11:04 AM
> To: Jakarta Commons Developers List
> Subject: Re: [lang] enhanced version of Class.forName
>=20
> James Carman wrote:
> > Do you think we need to go through the trouble of throwing an
> > IllegalArgumentException if it's not a well-formed class name
(starts
> with
> > character, blah blah blah)?  Or, can we just let it throw a
> > ClassNotFoundException after doing as much as we can with the string
> that's
> > passed in (i.e. transforming it into the proper format)?
>=20
> I was going to make this suggestion, that seems good enough to me.
>=20
> Emmanuel Bourg
>=20
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: commons-dev-unsubscribe@jakarta.apache.org
> For additional commands, e-mail: commons-dev-help@jakarta.apache.org
>=20
>=20
>=20
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: commons-dev-unsubscribe@jakarta.apache.org
> For additional commands, e-mail: commons-dev-help@jakarta.apache.org
>=20


---------------------------------------------------------------------
To unsubscribe, e-mail: commons-dev-unsubscribe@jakarta.apache.org
For additional commands, e-mail: commons-dev-help@jakarta.apache.org