Re: Problem with invoke call from Java

[Olaf Lüke]

Sorry for the late answer, at first i didn't see your post. Please add
my Email address as CC, since i am not actually subscribed to the
mailing list.

> I suppose you upgraded Octave from 3.6.4 to 3.8.1, not from 2.6.4 to 
> 2.8.1? 
Yes, i meant 3.*.*

> What Java version do you have installed? 32 or 64 bit? 
I tested on both 32 and 64 bit.

> 32 or 64 bit OS? 
I tested on 32 bit hardware with 32 bit OS and on 64 bit hardware with
64 bit OS.

> Another thing (that you do not mention): did you try to install the OF
> Java package in 3.8.1? (3.8.1 should have Java support built in). What
> does: 
> octave_config_info ("features").JAVA 
> give? 
octave:1> octave_config_info ("features").JAVA
ans =  1

> The exception mentions: 
> org.octave.Octave.doInvoke(I[Ljava/lang/Object;)V 
> which contains intruiging syntax ("I[L" and a trailing "V") 
> Could there be a code page or locale issue? 
I am no Java expert so i am not sure what these characters mean. But i
think i have seen them before in other Exceptions. So i don't think it
has anything to do with the problem. If i start octave with "LANG=EN" i
get the same exception.

> I tried a few commands from the examples in 
>
http://www.tinkerforge.com/en/doc/Software/Bricklets/AnalogIn_Bricklet_MATLAB.html#analog-in-bricklet-matlab-examples;
 > it just works fine til the ipcon.connect statement, as obviously I
> have no suitable hardware installed here. (And I suppose it is part of
> the first two parts that work for you as well). 
> Note: I use javaObject rather than java_new (should be in OF
> java-1.2.8 as well; OF-java is (was) at 1.2.9)
We should replace java_new with javaObject in the examples, yes. But
that is not the problem, java_new is deprecated but still implemented in
the newest octave version.

> So would you have a few lines of code that do not need the HW and that
> do show the problem? 
I reproduced the problem with a minimal example:
http://download.tinkerforge.com/_stuff/octave/

How i compiled it is described in the comments of the files. I also
attached the .class that i used for testing. Perhaps you can try to
compile it yourself and also try to use my .class. This way we can find
out if my Java environment has a problem.

> Finally, I'd say if it worked in 3.6.4 & OF-Java, it should work in
> 3.8.1 w built-in Java support. 
I agree, but it doesn't :-). Iit is probably just some small thing that
i am overlooking.

Thank you for the help!

Olaf Lüke