|
From: Stephen F. <sj...@us...> - 2008-09-09 13:00:05
|
Try adding the following code to your program; this forces WALA to process
the java.sql initialization sequence. You can substitute whatever driver
Derby provides for JdbcOdbcDriver().
static {
try {
java.sql.DriverManager.registerDriver(new
JdbcOdbcDriver());
} catch (SQLException e) {
e.printStackTrace();
}
}
------------------------------------------------------------------------
Stephen Fink
IBM T.J. Watson Research Center
sj...@us...
(914)784-7776
"Yao Qi" <qiy...@gm...>
Sent by: wal...@li...
09/09/2008 07:24 AM
Please respond to
WALA discussion and Q&A <wal...@li...>
To
"WALA discussion and Q&A" <wal...@li...>
cc
Subject
[Wala-wala] Fail to build call graph for JDBC driver code
When we run WALA on derby, the call graph we got doesn't contains any
derby classes. The harness program(JavaDBDemo.java in attachment) is
very simple, just load JDBC driver via Class.forName(), connect to
data base via DriverManager.getConnection(), perform some operations
and close the connection finally.
Seems WALA works well for reflection, but don't know WALA supports
such case. Is it a bug in WALA or WALA doesn't support such case at
all? If WALA doesn't support it, is there any workaround for this
problem?
--
Yao Qi
GNU/Linux Developer
[attachment "JavaDBDemo.java" deleted by Stephen Fink/Watson/IBM]
-------------------------------------------------------------------------
This SF.Net email is sponsored by the Moblin Your Move Developer's
challenge
Build the coolest Linux based applications with Moblin SDK & win great
prizes
Grand prize is a trip for two to an Open Source event anywhere in the
world
http://moblin-contest.org/redirect.php?banner_id=100&url=/
_______________________________________________
Wala-wala mailing list
Wal...@li...
https://lists.sourceforge.net/lists/listinfo/wala-wala
|