You are viewing a plain text version of this content. The canonical link for it is here.
Posted to j-users@xerces.apache.org by Michael Glavassevich <mr...@ca.ibm.com> on 2009/10/09 14:52:51 UTC
Re: Xerces versus TraX versus JDK 1.6 on Mac
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 <bi...@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?
Re: Xerces versus TraX versus JDK 1.6 on Mac
Posted by Michael Glavassevich <mr...@ca.ibm.com>.
Benson Margulies <bi...@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 <bi...@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
Re: Xerces versus TraX versus JDK 1.6 on Mac
Posted by Michael Glavassevich <mr...@ca.ibm.com>.
Benson Margulies <bi...@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 <bi...@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
Re: Xerces versus TraX versus JDK 1.6 on Mac
Posted by Benson Margulies <bi...@gmail.com>.
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 <mr...@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 <bi...@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?
>
>