Holger,
  I just got around to trying your solution, and it seems to me that
you think I'm using java 1.3. I'm not - I'm using Java 6:
$ java -version
java version "1.6.0_03"
Java(TM) SE Runtime Environment (build 1.6.0_03-b05)
Java HotSpot(TM) Client VM (build 1.6.0_03-b05, mixed mode, sharing)

Did I misunderstand you?
    ~Elizabeth


On Wed, Apr 9, 2008 at 8:58 AM, Holger Hoffstaette <[EMAIL PROTECTED]> wrote:
> On Tue, 08 Apr 2008 14:58:06 -0400, Elizabeth Clause wrote:
>
>  > I just updated my Xerces jar, and this code, which worked
>  > xercesImpl-2.6.2.jar, broke when I updated to xercesImpl-2.8.1.jar. I also
>  > tried updating to xercesImpl-2.9.0.jar, and got the same error. Here is
>  > the stack trace:
>  > Caught: java.lang.IncompatibleClassChangeError: Class
>  > org.apache.xerces.parsers.AbstractSAXParser$AttributesProxy does not
>  > implement the requested interface org.xml.sax.Attributes
>  >         at NewSaxParserText.run(NewSaxParserText.groovy:6) at
>  >         NewSaxParserText.main(NewSaxParserText.groovy)
>
>  What happens here is most likely not what you think happens, and it is
>  also not _directly_ the fault of the updated jars. Look here:
>  http://xerces.apache.org/xerces2-j/faq-general.html#faq-4
>
>  So unless you either a) install an updated xerces via the endorsed
>  mechanism OR b) explicitly pass the SAX/DOMFactory properties, _it won't
>  work_. It only _seems_ to work with xerces 2.6.2 since that version is more 
> or
>  less the same as what's in the JDK; under the hood "the wrong thing" still
>  happens, sort of.
>
>  hth
>  Holger
>
>
>
>  ---------------------------------------------------------------------
>  To unsubscribe, e-mail: [EMAIL PROTECTED]
>  For additional commands, e-mail: [EMAIL PROTECTED]
>
>

---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]

Reply via email to