| Subject: | Can't locate object method "__validate_prototype" via package "JDBC" |
I'm building on OS X Snow Leopard, using Inline::Java 0.52, Java 1.6.0_15 (the system
default), and perl 5.10.0 (the system default). I see the following failure:
% Build test
t/00-load.........ok 1/1# Testing JDBC 0.01, Perl 5.010000, /usr/bin/perl
t/00-load.........ok
t/01-driver.......Use of uninitialized value in split at t/test_init.pl line 20.
Can't locate object method "__validate_prototype" via package "JDBC" at (eval 25) line 344,
<GEN8> line 5.
t/01-driver.......ok 1/4# Looks like you planned 4 tests but only ran 1.
# Looks like your test died just after 1.
t/01-driver.......dubious
Test returned status 255 (wstat 65280, 0xff00)
DIED. FAILED tests 2-4
Failed 3/4 tests, 25.00% okay
t/02-connect......Use of uninitialized value in split at t/test_init.pl line 20.
Can't locate object method "__validate_prototype" via package "JDBC" at (eval 25) line 436,
<GEN8> line 5.
t/02-connect......ok 1/3# Looks like you planned 3 tests but only ran 1.
# Looks like your test died just after 1.
t/02-connect......dubious
Test returned status 255 (wstat 65280, 0xff00)
DIED. FAILED tests 2-3
Failed 2/3 tests, 33.33% okay
t/02-const........Use of uninitialized value in split at t/test_init.pl line 20.
t/02-const........ok
t/03-statement....Use of uninitialized value in split at t/test_init.pl line 20.
Can't locate object method "__validate_prototype" via package "JDBC" at (eval 25) line 436,
<GEN8> line 5.
t/03-statement....ok 1/3# Looks like you planned 3 tests but only ran 1.
# Looks like your test died just after 1.
t/03-statement....dubious
Test returned status 255 (wstat 65280, 0xff00)
DIED. FAILED tests 2-3
Failed 2/3 tests, 33.33% okay
t/pod-coverage....skipped
all skipped: Test::Pod::Coverage 1.04 required for testing POD coverage
t/pod.............ok
Failed Test Stat Wstat Total Fail List of Failed
-----------------------------------------------------------------------
--------
t/01-driver.t 255 65280 4 6 2-4
t/02-connect.t 255 65280 3 4 2-3
t/03-statement.t 255 65280 3 4 2-3
1 test skipped.
Failed 3/7 test scripts. 7/18 subtests failed.
Files=7, Tests=18, 5 wallclock secs ( 6.24 cusr + 0.88 csys = 7.12 CPU)
Failed 3/7 test programs. 7/18 subtests failed.
When I walk through the debugger in t/01-driver.t, I see that the failure is within JDBC-
Show quoted text
>getLoginTimeout. I'm guessing that any class method inherited from Inline::Java::Object
(via java::sql::DriverManager) is broken.
-Ken