[ http://issues.apache.org/jira/browse/DERBY-398?page=all ]
Deepa Remesh updated DERBY-398:
-------------------------------
Attachment: jdbcapi_lang_patch.diff
jdbcapi_lang_patch.status
Attaching a patch 'jdbcapi_lang_patch.diff' for enabling some tests to run with
J2ME/CDC/FP. Changes for each test are:
* jdbcapi/metadata.java and jdbcapi/odbc_metadata.java - Modified the tests to
use ij.startJBMS to get connection. Modified metadata_test.java by adding catch
block with 'NoSuchMethodError' around DatabaseMetaData.getURL because this
method is not available in JSR169. Also, call to procedure with nested
connection is not made when running with JSR169. Updated master files.
* jdbcapi/metaDataMultiConn.java - Commented out the line
Class.forName("org.apache.derby.jdbc.EmbeddedDriver"); to allow the test to run
with JSR169.
* jdbcapi/bestrowidentifier.sql - Added comment to _app.properties file to
indicate reason for excluding - test uses procedure with nested connection for
calling getBestRowIdentifier.
* jdbcapi/secureUsers1.sql - Added comment to _app.properties file to indicate
reason for excluding - test requires ldap support which is not available with
j9_foundation.
* lang/authorize.sql - Added comment to _app.properties file indicating
excluded for now - test uses server-side JDBC. This test can be split to take
out parts which can run with JSR169.
* lang/connect.sql - Added comment to _app.properties file indicating excluded
for now - test uses ij 'driver' command. This test can be split to take out
parts which can run with JSR169.
* lang/currentSchema.sql - Removed the protocol part from URLs in connect
statement to make it work in J2ME. Also updated master file.
* lang/db2Compatibility.sql - Removed the protocol part from URLs in connect
statement to make it work in J2ME. Also updated master file.
* lang/joindeadlock.sql - Removed the protocol part from URLs in connect
statement to make it work in J2ME. Also updated master file.
* lang/errorCode.sql - Added comment to _app.properties file indicating
excluded for now - test uses ij 'driver' command. This test can be split to
take out parts which can run with JSR169.
* lang/GetPropertyInfoTest.java - Added comment to _app.properties file to
indicate reason for excluding - test uses Driver.getPropertyInfo method.
* lang/maxMemPerTab.sql - Added comment to _app.properties file to indicate
reason for excluding - test uses server-side JDBC.
* lang/nestedcommit.sql - Added comment to _app.properties file to indicate
reason for excluding - test uses server-side JDBC.
Ran derbyall with Sun J2SE 1.4.2. Ran jdbcapi and derbylang suites with
j9_foundation VM in IBM WCTME 5.7. No new failures. This patch modifies tests
only. Please review/commit this patch.
> Exclude tests for J2ME/CDC/Foundation platform
> ----------------------------------------------
>
> Key: DERBY-398
> URL: http://issues.apache.org/jira/browse/DERBY-398
> Project: Derby
> Type: Sub-task
> Components: Test
> Reporter: Deepa Remesh
> Assignee: Deepa Remesh
> Attachments: derby-398_2.diff, derby-398_2.status, derbyall_report_2.txt,
> jdbcapi_lang_patch.diff, jdbcapi_lang_patch.status, nullSQLText_patch.diff,
> nullSQLText_patch.status, readme_patch.diff
>
> Exclude tests which use DriverManager, Driver or BigDecimal classes which are
> not in J2ME or JSR169. Ensure that derbyall can be run successfully in
> J2ME/CDC/Foundation platform using the JDBC Optional Package for
> CDC/Foundation Profile (JSR169).
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators:
http://issues.apache.org/jira/secure/Administrators.jspa
-
For more information on JIRA, see:
http://www.atlassian.com/software/jira
