You are viewing a plain text version of this content. The canonical link for it is here.
Posted to derby-dev@db.apache.org by "Knut Anders Hatlen (JIRA)" <ji...@apache.org> on 2010/05/23 18:28:25 UTC
[jira] Created: (DERBY-4674) BooleanValuesTest fails if Xalan is
not available
BooleanValuesTest fails if Xalan is not available
-------------------------------------------------
Key: DERBY-4674
URL: https://issues.apache.org/jira/browse/DERBY-4674
Project: Derby
Issue Type: Bug
Components: Test
Affects Versions: 10.7.0.0
Reporter: Knut Anders Hatlen
Assignee: Knut Anders Hatlen
If Xalan is not available, BooleanValuesTest fails. See for example this error log from the nightly testing:
http://dbtg.foundry.sun.com/derby/test/Daily/jvm1.4/testing/Limited/testSummary-947309.html
The error above is actually caused by the Xalan version bundled with J2SE 1.4.2 being too old for Derby, not that it's missing. Here's what the error looks like on Java SE 6 without xalan.jar in the classpath:
1) test_01_datatypeCount(org.apache.derbyTesting.functionTests.tests.lang.BooleanValuesTest)java.sql.SQLException: Failed to locate 'Xalan' API or implementation classes. XML operations are not permitted unless these classes are in your classpath.
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
[jira] Resolved: (DERBY-4674) BooleanValuesTest fails if Xalan is
not available
Posted by "Knut Anders Hatlen (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/DERBY-4674?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Knut Anders Hatlen resolved DERBY-4674.
---------------------------------------
Fix Version/s: 10.7.0.0
Resolution: Fixed
Committed revision 947442.
> BooleanValuesTest fails if Xalan is not available
> -------------------------------------------------
>
> Key: DERBY-4674
> URL: https://issues.apache.org/jira/browse/DERBY-4674
> Project: Derby
> Issue Type: Bug
> Components: Test
> Affects Versions: 10.7.0.0
> Reporter: Knut Anders Hatlen
> Assignee: Knut Anders Hatlen
> Fix For: 10.7.0.0
>
> Attachments: check-xalan.diff
>
>
> If Xalan is not available, BooleanValuesTest fails. See for example this error log from the nightly testing:
> http://dbtg.foundry.sun.com/derby/test/Daily/jvm1.4/testing/Limited/testSummary-947309.html
> The error above is actually caused by the Xalan version bundled with J2SE 1.4.2 being too old for Derby, not that it's missing. Here's what the error looks like on Java SE 6 without xalan.jar in the classpath:
> 1) test_01_datatypeCount(org.apache.derbyTesting.functionTests.tests.lang.BooleanValuesTest)java.sql.SQLException: Failed to locate 'Xalan' API or implementation classes. XML operations are not permitted unless these classes are in your classpath.
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
[jira] Closed: (DERBY-4674) BooleanValuesTest fails if Xalan is not
available
Posted by "Knut Anders Hatlen (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/DERBY-4674?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Knut Anders Hatlen closed DERBY-4674.
-------------------------------------
Thanks Rick. The test appears to be running fine on 1.4.2 now, and also on Java 6 without Xalan in the classpath. Closing the issue.
> BooleanValuesTest fails if Xalan is not available
> -------------------------------------------------
>
> Key: DERBY-4674
> URL: https://issues.apache.org/jira/browse/DERBY-4674
> Project: Derby
> Issue Type: Bug
> Components: Test
> Affects Versions: 10.7.0.0
> Reporter: Knut Anders Hatlen
> Assignee: Knut Anders Hatlen
> Fix For: 10.7.0.0
>
> Attachments: check-xalan.diff, derby-4674-02-aa-noXML.diff
>
>
> If Xalan is not available, BooleanValuesTest fails. See for example this error log from the nightly testing:
> http://dbtg.foundry.sun.com/derby/test/Daily/jvm1.4/testing/Limited/testSummary-947309.html
> The error above is actually caused by the Xalan version bundled with J2SE 1.4.2 being too old for Derby, not that it's missing. Here's what the error looks like on Java SE 6 without xalan.jar in the classpath:
> 1) test_01_datatypeCount(org.apache.derbyTesting.functionTests.tests.lang.BooleanValuesTest)java.sql.SQLException: Failed to locate 'Xalan' API or implementation classes. XML operations are not permitted unless these classes are in your classpath.
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
[jira] Updated: (DERBY-4674) BooleanValuesTest fails if Xalan is
not available
Posted by "Knut Anders Hatlen (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/DERBY-4674?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Knut Anders Hatlen updated DERBY-4674:
--------------------------------------
Attachment: check-xalan.diff
check-xalan.diff makes BooleanValuesTest's suite() method check if we have the required XML libraries before running the test. If we don't, the test is skipped. I'll commit shortly to get the nightly tests to run cleanly again.
> BooleanValuesTest fails if Xalan is not available
> -------------------------------------------------
>
> Key: DERBY-4674
> URL: https://issues.apache.org/jira/browse/DERBY-4674
> Project: Derby
> Issue Type: Bug
> Components: Test
> Affects Versions: 10.7.0.0
> Reporter: Knut Anders Hatlen
> Assignee: Knut Anders Hatlen
> Attachments: check-xalan.diff
>
>
> If Xalan is not available, BooleanValuesTest fails. See for example this error log from the nightly testing:
> http://dbtg.foundry.sun.com/derby/test/Daily/jvm1.4/testing/Limited/testSummary-947309.html
> The error above is actually caused by the Xalan version bundled with J2SE 1.4.2 being too old for Derby, not that it's missing. Here's what the error looks like on Java SE 6 without xalan.jar in the classpath:
> 1) test_01_datatypeCount(org.apache.derbyTesting.functionTests.tests.lang.BooleanValuesTest)java.sql.SQLException: Failed to locate 'Xalan' API or implementation classes. XML operations are not permitted unless these classes are in your classpath.
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
[jira] Updated: (DERBY-4674) BooleanValuesTest fails if Xalan is
not available
Posted by "Rick Hillegas (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/DERBY-4674?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Rick Hillegas updated DERBY-4674:
---------------------------------
Attachment: derby-4674-02-aa-noXML.diff
Thanks for getting this test fixed on 1.4, Knut. I am committing a further improvement: derby-4674-02-aa-noXML.diff. This patch re-enables BooleanValuesTest on jdk 1.4. Now the test avoids the XML datatype if it is not supported by the test configuration.
Committed at subversion revision 947656.
Touches the following files:
M java/testing/org/apache/derbyTesting/functionTests/tests/lang/BooleanValuesTest.java
> BooleanValuesTest fails if Xalan is not available
> -------------------------------------------------
>
> Key: DERBY-4674
> URL: https://issues.apache.org/jira/browse/DERBY-4674
> Project: Derby
> Issue Type: Bug
> Components: Test
> Affects Versions: 10.7.0.0
> Reporter: Knut Anders Hatlen
> Assignee: Knut Anders Hatlen
> Fix For: 10.7.0.0
>
> Attachments: check-xalan.diff, derby-4674-02-aa-noXML.diff
>
>
> If Xalan is not available, BooleanValuesTest fails. See for example this error log from the nightly testing:
> http://dbtg.foundry.sun.com/derby/test/Daily/jvm1.4/testing/Limited/testSummary-947309.html
> The error above is actually caused by the Xalan version bundled with J2SE 1.4.2 being too old for Derby, not that it's missing. Here's what the error looks like on Java SE 6 without xalan.jar in the classpath:
> 1) test_01_datatypeCount(org.apache.derbyTesting.functionTests.tests.lang.BooleanValuesTest)java.sql.SQLException: Failed to locate 'Xalan' API or implementation classes. XML operations are not permitted unless these classes are in your classpath.
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.