I don't follow why this is necessary. If we just remove javax.xml.transform.TransformerFactory from xml-apis.jar then the jdk bundled TransformerFactory will be used to choose the correct implementation.
A user can always drop his own xalan.jar to lib/endorsed (for jdk1.4/5), or server/xxx/lib for jdk5, or use a scoped xalan.jar to override the jdk version, since xalan.jar contains: META-INF/services/javax.xml.transform.TransformerFactory file containing the class name of its implementation. > -----Original Message----- > From: [EMAIL PROTECTED] > [mailto:[EMAIL PROTECTED] On > Behalf Of Scott M Stark > Sent: 22 February, 2006 18:16 > To: jboss-development@lists.sourceforge.net > Subject: RE: [JBoss-dev] Xalan removal saga > > Setting this via a system property cannot be done as this is > a global override. We could simply externalize the default > factory name to an attribute of the jboss server info mbean > and fallback to the jdk default if it cannot be found. I > don't know if an extension class can get access to a class > from the jdk rt.jar via the ClassLoader.getSystemClassLoader(). ------------------------------------------------------- This SF.net email is sponsored by: Splunk Inc. Do you grep through log files for problems? Stop! Download the new AJAX search engine that makes searching your log files as easy as surfing the web. DOWNLOAD SPLUNK! http://sel.as-us.falkag.net/sel?cmd=lnk&kid3432&bid#0486&dat1642 _______________________________________________ JBoss-Development mailing list JBoss-Development@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/jboss-development
