I traced this down to a TranformerFactory included in the xml-apis.jar that comes with xerces tools (e.g. Xerces-J-tools.2.7.1.zip).
This is tagged as 1.3.02 and in turn originates from http://xml.apache.org/commons/ The xml-commons hadn't had any releases for some time, so the tagged xml-apis.jar comes directly from their cvs. I think I will remove all javax.xml.transform.** from xml-apis.jar to create a new xml-apis-no-transform.jar and include this instead. >From a quick test it seems to be working with both jdk1.4 and jdk5. > -----Original Message----- > From: [EMAIL PROTECTED] > [mailto:[EMAIL PROTECTED] On > Behalf Of Scott M Stark > Sent: 21 February, 2006 21:08 > To: jboss-development@lists.sourceforge.net > Subject: RE: [JBoss-dev] Xalan removal saga > > The question is where the the xml-apis.jar come from then? It > should not include a TransformerFactory if its not from the > xalan distribution which is what I suspect. The origin of the > xml jars needs to be validated and if the xerces distribution > defaults to configuring a TransformerFactory, that should be removed. > > The xml parser is needed to override the buggy jdk version. ------------------------------------------------------- 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