> I had the same problem when I decided to put my classes into a package
> with a name containing an underscore (com.origin_it.)
> 0005f is probably either the unicode or ascii code for the underscore.
> IU asked a question to the guys at JavaSoft if this is normal behaviour
> or not, but I did not get any reply yet.
Argh! And I thought there was no difference between the classes that
worked and those that didn't. You're dead right - the classes that don't
work contain an '_' in the *class name*!!!
So it seems like if there is an '_' in the package name or the class name,
then, although the classes compile OK, the stubs generator will replace
the '_' with '_0005f' (Note that the '_' is still there as well!!).
I must assume the obvious: - that the use of the '_' in all native library
stubs (the JNI uses '_' insteadof '.' in package paths) precludes it's use
in the actual class names.
Seems obvious in retrospect (in fact I even remember worrying about this
issue 8 months ago when I first tried out JNI), but it certainly didn't
occur to me last night when I was pulling my hair out.
Thanks a million, Craig
------
"In order to make an apple pie from scratch, you must first create the
universe."
-- Carl Sagan, Cosmos
======================================================================
Craig Taverner ------====== Email:[EMAIL PROTECTED]
ComOpt AB ------======== Tel: +46-42-212580
Michael Löfmans Gata 6 ------========== Fax: +46-42-210585
SE-254 38 Helsingborg ------======== Cell: +46-708-212598
Sweden ------====== http://www.comopt.com
======================================================================
