Hi, Joseph. What you wrote is what Sun intended to be the architecture. However I tried it once for Axis and Xerces since the rest of the application (huge project) relied on DOM level 1. The problem here is that even if you implement your own classloader, Xerces will have another one that loads classes via the system boot classloader rather than the self-made.
It's more work than one might think at the first glance. Hiran ----------------------------------------- Hiran Chaudhuri SAG Systemhaus GmbH Elsenheimerstra�e 11 80687 M�nchen Germany [EMAIL PROTECTED] Phone +49-89-54742-134 Fax +49-6151-9234-5134 > -----Original Message----- > From: Joseph Kesselman [mailto:[EMAIL PROTECTED] > Sent: Thursday, September 19, 2002 5:45 PM > To: [EMAIL PROTECTED] > Subject: Re: Xerces and Applets > > > > > > ---------- > > Von: Joseph Kesselman[SMTP:[EMAIL PROTECTED] > > Gesendet: Donnerstag, 19. September 2002 17:45:24 > > An: [EMAIL PROTECTED] > > Betreff: Re: Xerces and Applets > > Diese Nachricht wurde automatisch von einer Regel weitergeleitet. > > > As far as I know, if you want applets to be able to load > different classes > than those found by the surrounding application, the > application has to > load the applets using a classloader which implements that > alternative > classpath behavior. Otherwise, you will get whatever is > already loaded > and/or whatever the application would normally find. > > ______________________________________ > Joe Kesselman / IBM Research > > --------------------------------------------------------------------- > To unsubscribe, e-mail: [EMAIL PROTECTED] > For additional commands, e-mail: [EMAIL PROTECTED] > --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
