Sorry, your error description is not very clear. Perhaps it's best to
include code the next time.
But a guess what can be the problem: JNI requires additional characters
in the signature if methods are overloaded. Perhaps you have such
overloaded methods, but did not use the modified signature in your
native code. Each of them will work if it is the only one, bute they
will not work if they are together.
Matthias
Yuwin Fei wrote:
>
> Hi,
>
> I got an UnsatisfiedLinkErr exception in calling a second native method
> from Java (not a nested JNI call). I checked signature of the method and made
> sure they're consistent in both sides. It still happens. Anyone know what this
> error really means? Is there a limitation as to how many native methods one
> Java Object can have?
>
> I tested my JNI stuff with a single native method in various JNI
> interactions between the Java and Native functions, and so far everyting works
> fine until I introduced a second native method.
>
> Thanks in advance,
>
> ____________________________________________________________________
> Get your own FREE, personal Netscape WebMail account today at
>http://webmail.netscape.com.
>
> ----------------------------------------------------------------------
> To UNSUBSCRIBE, email to [EMAIL PROTECTED]
> with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
----------------------------------------------------------------------
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
