> In my opinion, this is a bad design decision. ClassLoaders are supposed to > delegate to their parent before attempting to load a class and the system > class loader (which loads the core libraries and all standard extensions) is > the parent of all classloaders. So, if you're worried about > javax.sql.DataSource being loaded from a rogue jar file, it won't! > > It will > be loaded by the system class loader since it can find it. So, this whole > idea of "trigger" classes is unnecessary! This should be removed, as it is > causing tremendous problems! As a workaround, all you have to do is remove > the javax.sql.* classes from your classes12.zip (in the case of the Oracle > JDBC drivers) file. But, this should not be necessary. Oracle should > remove the javax.sql.* files in later releases targeted for the JDK1.4, but > it shouldn't be a requirement.
As I said, please check the latest source (the triggers in ClassLoaderFactory was old code I forgot to remove :-(). As for the webapp repositories, they don't use the normal delegation model, so triggers are needed (for JAXP, JNDI, and the servlet API classes). Remy -- To unsubscribe, e-mail: <mailto:[EMAIL PROTECTED]> For additional commands, e-mail: <mailto:[EMAIL PROTECTED]>
