[prev in list] [next in list] [prev in thread] [next in thread] 

List:       xerces-j-dev
Subject:    Re: Xerces versus TraX versus JDK 1.6 on Mac
From:       Michael Glavassevich <mrglavas () ca ! ibm ! com>
Date:       2009-10-09 13:27:49
Message-ID: OF7D763D13.FACB068A-ON8525764A.0047BBB4-8525764A.0049F6E0 () ca ! ibm ! com
[Download RAW message or body]

Benson Margulies <bimargulies@gmail.com> wrote on 10/09/2009 08:56:10 AM:

> Michael,
>
> Would it be considered a goal of Xerces to work around this?

If Xerces is already behaving according to the spec it's the application's
(the JDK 6 Transfomer in this case) responsibility to use it correctly.
It's never been a goal to accommodate broken input / code. Quite the
opposite actually.

> In other words, would it be worth some actually analysis to find out
> what the fuss is about?

Perhaps, though probably worth avoiding the Sun JDK 6 impl altogether based
on other users' experience.

> 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 <mrglavas@ca.ibm.com
> > 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: mrglavas@ca.ibm.com
> E-mail: mrglavas@apache.org
>
> Benson Margulies <bimargulies@gmail.com> 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?

Thanks.

Michael Glavassevich
XML Parser Development
IBM Toronto Lab
E-mail: mrglavas@ca.ibm.com
E-mail: mrglavas@apache.org
[Attachment #3 (text/html)]

<html><body>
<p><tt>Benson Margulies &lt;bimargulies@gmail.com&gt; wrote on 10/09/2009 08:56:10 \
AM:<br> <br>
&gt; Michael,<br>
&gt; <br>
&gt; Would it be considered a goal of Xerces to work around this?</tt><br>
<br>
<tt>If Xerces is already behaving according to the spec it's the application's (the \
JDK 6 Transfomer in this case) responsibility to use it correctly. It's never been a \
goal to accommodate broken input / code. Quite the opposite actually.</tt><br> <br>
<tt>&gt; In other words, would it be worth some actually analysis to find out <br>
&gt; what the fuss is about?</tt><br>
<br>
<tt>Perhaps, though probably worth avoiding the Sun JDK 6 impl altogether based on \
other users' experience.</tt><br> <br>
<tt>&gt; Since the test case involves a SAXSource delivering a rather complex \
</tt><br> <tt>&gt; sequence of events from an HTML to XHTML converter, it would take \
some </tt><br> <tt>&gt; doing.<br>
&gt; <br>
&gt; --benson<br>
</tt><br>
<tt>&gt; On Fri, Oct 9, 2009 at 8:52 AM, Michael Glavassevich \
&lt;mrglavas@ca.ibm.com<br> &gt; &gt; wrote:</tt><br>
<tt>&gt; Benson,<br>
&gt; <br>
&gt; I've read / heard about several problems with the JAXP <br>
&gt; implementation in Sun JDK 6 and it's possible that this might be <br>
&gt; another one. I wouldn't assume that what you were seeing is an issue<br>
&gt; with Xerces.<br>
&gt; <br>
&gt; Thanks.<br>
&gt; <br>
&gt; Michael Glavassevich<br>
&gt; XML Parser Development<br>
&gt; IBM Toronto Lab<br>
&gt; E-mail: mrglavas@ca.ibm.com<br>
&gt; E-mail: mrglavas@apache.org<br>
&gt; <br>
&gt; Benson Margulies &lt;bimargulies@gmail.com&gt; wrote on 10/08/2009 10:11:06 \
PM:</tt><br> <tt>&gt; <br>
&gt; <br>
&gt; &gt; I had the following rather wierd experience:<br>
&gt; &gt; <br>
&gt; &gt; 1) Add Xerces 2.9.1 to classpath<br>
&gt; &gt; <br>
&gt; &gt; 2) TransformerFactory.newInstance().newTransformer().transform(new <br>
&gt; &gt; SAXSource(.....), new DOMResult());<br>
&gt; &gt; <br>
&gt; &gt; fails with DOMException, NOT_FOUND_ERR.<br>
&gt; &gt; <br>
&gt; &gt; 3) Adding Xalan to the path make it go away.<br>
&gt; &gt; <br>
&gt; &gt; Is this something to JIRA?</tt><br>
<br>
<tt>Thanks.</tt><br>
<br>
<tt>Michael Glavassevich<br>
XML Parser Development<br>
IBM Toronto Lab<br>
E-mail: mrglavas@ca.ibm.com</tt><br>
<tt>E-mail: mrglavas@apache.org</tt></body></html>



[prev in list] [next in list] [prev in thread] [next in thread] 

Configure | About | News | Add a list | Sponsored by KoreLogic