I'll work on a central class that will handle classloading for each of these three categories. I think that each one needs to be handled a little differently. Then, I'll redirect the existing stuff to point to the centralized ClassLoaderHelper class or whatever I call it. I'll keep it all JDK 1.1.x compatible.
One of my main goals is to provide a much better diagnostic message when the class cannot be found. I was thinking of org.apache.xml.utils.ClassLoaderHelper. Any comments? Gary > -----Original Message----- > From: Shane Curcuru [mailto:[EMAIL PROTECTED]] > Sent: Wednesday, July 17, 2002 7:17 AM > To: [EMAIL PROTECTED] > Subject: Re: Classloader issues > > > ---- you Gary L Peskin wrote ---- > > I'd appreciate any feedback or input that anyone has as we > start down > > this road. Suggested standards for each category, or refinements of > the > > categories or anything else. > > Whoo-hoo! Excellent analysis of the areas in Xalan that may > be affected by this issue. > > I suppose one simple work item for now could be to simply > move all loading stuff into a worker method, so we can > experiment with re-doing the implementation later. This > should be safe, it just takes work to > create the worker and re-do other code to point to it. > Note that we probably should address javax.xml.* loaders > separately. Note also that we should be careful for now to > keep JDK 1.1.x compatibility (let's argue that later; I'd > like to keep this thru Xalan-J 2.4 and then drop it after > that) and try to keep intra-Xalan-package dependencies down.
