Well, I found out the cause of the problem - both the main and subclassed
versions of the class used a utility class from another package (also
present in the resources directory). The main class and the [functional]
subclass both imported this package. The subclass that didn't work didn't.
When I added an explicit import line to the nonfunctional class, the problem
went away. I guess I'll take a look at the classloader code when I have a
few free minutes.
-----Original Message-----
From: jon * <[EMAIL PROTECTED]>
To: Java Apache Users <[EMAIL PROTECTED]>
Date: Wednesday, March 17, 1999 6:50 PM
Subject: Re: Resources vs. Classpath
>> Since this code is part of my company's product, I can't post it here. I
>> realize this does make it difficult for anyone to provide
trouble-shooting
>> suggestions.
>
>You have our code...so you should be able to debug the issue for us. ;-)
>
>-jon
>
>
>
>----------------------------------------------------------------
>To subscribe: [EMAIL PROTECTED]
>To unsubscribe: [EMAIL PROTECTED]
>Archives and Other: <http://java.apache.org/main/mail.html/>
>Problems?: [EMAIL PROTECTED]
>
>
----------------------------------------------------------------
To subscribe: [EMAIL PROTECTED]
To unsubscribe: [EMAIL PROTECTED]
Archives and Other: <http://java.apache.org/main/mail.html/>
Problems?: [EMAIL PROTECTED]
