db-derby-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Satheesh Bandaram <sathe...@Sourcery.Org>
Subject Re: XMLPARSE usage?
Date Tue, 14 Feb 2006 20:28:34 GMT
I think the problem is because of XMLTypeCompiler not being listed in
'extraDBMStypes.properties'. I looked at 10.2 snapshot derby.jar and I
don't find XMLTypeCompiler in the JAR.

I also tried earlier with classes and there is no problem there....

Satheesh

Army wrote:

>
> I'll try to find time to look at this.  Note that as part of my
> in-progress-but-currently-back-burnered work for the 10.2 release I
> will be enabling XML tests to run as part of derbyall, so this type of
> problem (where it only occurs against the jar files) will be caught in
> the regression tests.
>
> But in the meantime, thanks for bringing this to my attention.  If
> anyone out there knows what might be causing this NPE with the jars
> but not with classes, I'd appreciate any pointers...
>
> Army
>
> P.S. In case you're interested, I see the following results when using
> the "classes" directory.  Note that the changes I hope to make for the
> 10.2 release will catch the "class not found" type of exceptions and
> print something more friendly.  In the meantime, though:
>
> Sun 1.3 (expected failure because XML interfaces aren't part of 1.3):
>
> ERROR 38000: The exception 'java.lang.NoClassDefFoundError:
> org/xml/sax/ErrorHandler' was thrown while evaluating an expression.
> ERROR XJ001: Java exception: 'org/xml/sax/ErrorHandler:
> java.lang.NoClassDefFoundError'.
>
> IBM 1.3 (expected failure because XML interfaces aren't part of 1.3):
>
> ERROR 38000: The exception 'java.lang.NoClassDefFoundError:
> javax/xml/transform/Result' was thrown while evaluating an expression.
> ERROR XJ001: Java exception: 'javax/xml/transform/Result:
> java.lang.NoClassDefFoundError'.
>
> Sun 1.4.2, 1.5:
>
> ERROR 2200L: XMLPARSE operand is not an XML document; see next
> exception for details.
> ERROR XJ001: Java exception: 'SAX2 driver class
> org.apache.xerces.parsers.SAXParser not found: org.xml.sax.SAXException'.
>
> This is an expected error if I don't have Xerces in my classpath; if I
> put Xerces in my classpath (i.e. just include xercesImpl.jar), then
> the insert statement succeeds.
>
> IBM 1.4.2:
>
> Statement succeeds (because Xerces is part of the IBM 1.4.2 jvm).
>
>
>


Mime
View raw message