[
https://issues.apache.org/jira/browse/DERBY-3803?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12617914#action_12617914
]
Kathey Marsden commented on DERBY-3803:
---------------------------------------
The actual exception is:
javax.xml.parsers.FactoryConfigurationError: Provider
org.apache.xerces.jaxp.DocumentBuilderFactoryImpl not found
at
javax.xml.parsers.DocumentBuilderFactory.newInstance(DocumentBuilderFactory.java:104)
at org.apache.derby.iapi.types.SqlXmlUtil.<init>(SqlXmlUtil.java:175)
at
org.apache.derby.impl.sql.compile.UnaryOperatorNode.bindXMLParse(UnaryOperatorNode.java:390)
at
org.apache.derby.impl.sql.compile.UnaryOperatorNode.bindExpression(UnaryOperatorNode.java:316)
at
org.apache.derby.impl.sql.compile.ResultColumn.bindExpression(ResultColumn.java:588)
at
org.apache.derby.impl.sql.compile.ResultColumnList.bindExpressions(ResultColumnList.java:693)
at
org.apache.derby.impl.sql.compile.RowResultSetNode.bindExpressions(RowResultSetNode.java:238)
at
org.apache.derby.impl.sql.compile.DMLStatementNode.bindExpressions(DMLStatementNode.java:227)
at
org.apache.derby.impl.sql.compile.InsertNode.bindStatement(InsertNode.java:307)
at
org.apache.derby.impl.sql.GenericStatement.prepMinion(GenericStatement.java:314)
at
org.apache.derby.impl.sql.GenericStatement.prepare(GenericStatement.java:88)
at
org.apache.derby.impl.sql.conn.GenericLanguageConnectionContext.prepareInternalStatement(GenericLanguageConnectionContext.java:794)
at
org.apache.derby.impl.jdbc.EmbedStatement.execute(EmbedStatement.java:606)
at
org.apache.derby.impl.jdbc.EmbedStatement.executeUpdate(EmbedStatement.java:175)
at
org.apache.derby.impl.drda.DRDAConnThread.parseEXCSQLIMM(DRDAConnThread.java:5019)
at
org.apache.derby.impl.drda.DRDAConnThread.processCommands(DRDAConnThread.java:750)
at
org.apache.derby.impl.drda.DRDAConnThread.run(DRDAConnThread.java:290)
> 'org.apache.derbyTesting.functionTests.tests.lang.XMLTypeAndOpsTest' failures
> on JVM 1.5 on trunk, 10.4 and 10.3
> ----------------------------------------------------------------------------------------------------------------
>
> Key: DERBY-3803
> URL: https://issues.apache.org/jira/browse/DERBY-3803
> Project: Derby
> Issue Type: Bug
> Components: Regression Test Failure
> Affects Versions: 10.3.3.1, 10.4.1.4, 10.5.0.0
> Environment: JVM: Sun Microsystems Inc.
> java version "1.5.0_14"
> Java(TM) 2 Runtime Environment, Standard Edition (build 1.5.0_14-b03)
> Java HotSpot(TM) Server VM (build 1.5.0_14-b03 mixed mode 32-bit)
> Reporter: Ole Solberg
> Assignee: Kathey Marsden
>
> Since r676008 (2008-07-11 18:01:05 MEST) regression tests on Jvm 1.5 has
> failed on trunk, 10.4 and 10.3 in suitesAll /
> org.apache.derbyTesting.functionTests.tests.lang.XMLTypeAndOpsTest with
> 1)
> testXMLCasting(org.apache.derbyTesting.functionTests.tests.lang.XMLTypeAndOpsTest)java.sql.SQLException:
> Table/View 'NONXTABLE' already exists in Schema 'APP'.
> 2)
> testXMLSerialize(org.apache.derbyTesting.functionTests.tests.lang.XMLTypeAndOpsTest)java.sql.SQLException:
> Table/View 'VCTAB' already exists in Schema 'APP'.
> 3)
> testXMLQueryInsert(org.apache.derbyTesting.functionTests.tests.lang.XMLTypeAndOpsTest)java.sql.SQLException:
> Failed to locate 'JAXP' API or implementation classes. XML operations are
> not permitted unless these classes are in your classpath.
> 4)
> testXMLQueryUpdate(org.apache.derbyTesting.functionTests.tests.lang.XMLTypeAndOpsTest)java.sql.SQLException:
> Failed to locate 'JAXP' API or implementation classes. XML operations are
> not permitted unless these classes are in your classpath.
> 5)
> testAttrSerialization(org.apache.derbyTesting.functionTests.tests.lang.XMLTypeAndOpsTest)java.sql.SQLException:
> Failed to locate 'JAXP' API or implementation classes. XML operations are
> not permitted unless these classes are in your classpath.
> 6)
> testTriggerSPSWithXML(org.apache.derbyTesting.functionTests.tests.lang.XMLTypeAndOpsTest)java.sql.SQLException:
> Failed to locate 'JAXP' API or implementation classes. XML operations are
> not permitted unless these classes are in your classpath.
> 1)
> testNonXMLColsWithXMLVals(org.apache.derbyTesting.functionTests.tests.lang.XMLTypeAndOpsTest)junit.framework.ComparisonFailure:
> Unexpected SQL state. expected:<[42821]> but was:<[XML00]>
> 2)
> testXMLParse(org.apache.derbyTesting.functionTests.tests.lang.XMLTypeAndOpsTest)junit.framework.ComparisonFailure:
> Unexpected SQL state. expected:<[42X25]> but was:<[XML00]>
> 3)
> testTopLevelSelect(org.apache.derbyTesting.functionTests.tests.lang.XMLTypeAndOpsTest)junit.framework.ComparisonFailure:
> Unexpected SQL state. expected:<[42Z71]> but was:<[XML00]>
> 4)
> testXMLParseSerializeCombos(org.apache.derbyTesting.functionTests.tests.lang.XMLTypeAndOpsTest)junit.framework.ComparisonFailure:
> Unexpected SQL state. expected:<[2200M]> but was:<[XML00]>
> 5)
> testXMLExists(org.apache.derbyTesting.functionTests.tests.lang.XMLTypeAndOpsTest)junit.framework.ComparisonFailure:
> Unexpected SQL state. expected:<[42Z77]> but was:<[XML00]>
> 6)
> testXMLQuery(org.apache.derbyTesting.functionTests.tests.lang.XMLTypeAndOpsTest)junit.framework.ComparisonFailure:
> Unexpected SQL state. expected:<[42Z71]> but was:<[XML00]>
> 7)
> testNestedXMLQuery(org.apache.derbyTesting.functionTests.tests.lang.XMLTypeAndOpsTest)junit.framework.ComparisonFailure:
> Unexpected SQL state. expected:<[2200V]> but was:<[XML00]>
> 8)
> testInvalidXMLBindings(org.apache.derbyTesting.functionTests.tests.lang.XMLBindingTest)junit.framework.ComparisonFailure:
> Unexpected SQL state. expected:<[42Z7]0> but was:<[XML0]0>
> See e.g.
> http://dbtg.thresher.com/derby/test/Daily/jvm1.5/testing/Limited/testSummary-676008.html
> http://dbtg.thresher.com/derby/test/10.4Branch/jvm1.5/testing/Limited/testSummary-676639.html
> and
> http://dbtg.thresher.com/derby/test/debug/10.3Branch_logfile_org.apache.derbyTesting.functionTests.tests.lang.XMLTypeAndOpsTest.out
> The failure appears to be introduced by svn r675956 (Fri Jul 11 07:07:51 PDT
> 2008): derby-3745_trunk_diff.txt.
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
