Michael, Would it be considered a goal of Xerces to work around this? In other words, would it be worth some actually analysis to find out what the fuss is about? Since the test case involves a SAXSource delivering a rather complex sequence of events from an HTML to XHTML converter, it would take some doing.
--benson On Fri, Oct 9, 2009 at 8:52 AM, Michael Glavassevich <[email protected]>wrote: > Benson, > > I've read / heard about several problems with the JAXP implementation in > Sun JDK 6 and it's possible that this might be another one. I wouldn't > assume that what you were seeing is an issue with Xerces. > > Thanks. > > Michael Glavassevich > XML Parser Development > IBM Toronto Lab > E-mail: [email protected] > E-mail: [email protected] > > Benson Margulies <[email protected]> wrote on 10/08/2009 10:11:06 PM: > > > > I had the following rather wierd experience: > > > > 1) Add Xerces 2.9.1 to classpath > > > > 2) TransformerFactory.newInstance().newTransformer().transform(new > > SAXSource(.....), new DOMResult()); > > > > fails with DOMException, NOT_FOUND_ERR. > > > > 3) Adding Xalan to the path make it go away. > > > > Is this something to JIRA? > >
