This is very, very bad practice from a performance perspective (in fact,
everyone should expect to spend time in the next development cycle
reducing the number of caught exceptions like this).
The other way to do it -- call the methods individually and check to see
if they return a null pointer before continuing -- may be a little more
typing, but it is far preferable.
-Scott
On Mon, 2006-03-20 at 17:52, vince kraemer wrote:
> This seems like a bad practice...
>
> See:
> http://fisheye5.cenqua.com/viewrep/glassfish/appserv-core/src/java/com/sun/enterprise/resource/ResourcesXMLParser.java?r1=1.4&r2=1.5
>
> Is there another way to code this?
>
> vbk
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: dev-unsubscribe_at_glassfish.dev.java.net
> For additional commands, e-mail: dev-help_at_glassfish.dev.java.net
>