By using this site, you agree to our updated Privacy Policy and our Terms of Use. Manage your Cookies Settings.
454,278 Members | 1,502 Online
Bytes IT Community
+ Ask a Question
Need help? Post your question and get tips & solutions from a community of 454,278 IT Pros & Developers. It's quick & easy.

IllegalAccessError since db2 9 and java 1.5

P: n/a

since we upgraded to db2 v9 and java 1.5 we get an illegal access error
if we call a method of another stored procedure class, located in
another .jar file, from one stored procedure (by call I mean calling
the java-method directly from java). With db2 v8.2 and java 1.4 this
worked fine.

Now I'd like to know if there is a switch we could turn on, to prevent
that exception being raised or if there is another way of calling one
java stored procedure from another, without using the call statement
(we don't want to have to go another extra roundtrip through the
database; also you can use different interfaces for ther internally
used method and the externally available sp).

Any information/comments would be appreciated.


Oct 9 '06 #1
Share this Question
Share on Google+
1 Reply

P: n/a
Stupid me! We had protected modifier before the methods; and althought
they were in the same package, java 1.5 seems to be more restrictive if
they are in different .jar files!

Sorry for spaming the newsgroup ;)


Oct 9 '06 #2

This discussion thread is closed

Replies have been disabled for this discussion.