DLL Wrapper works when functions called out of main(), not from elsewhere?

Question

Hello all,
I am currently trying the JSAsio wrapper out ( http://sourceforge.net/projects/jsasio )
Support on this project is nearly unexisting and a lot of people seem to complain that it doesn't work well.
It works very nicely here, I wrote a few test classes which called some functions (like playing a sound or recording it) and had no problems whatsoever.
These test classes were all static functions and ran straight out of the main() method and printed some results to the console.
     public static void main(String[] args)
          boolean result = callFunction();
          .. end..
     public static boolean callFunction()
          initASIO();
          openASIOLine();
          return true;
     }The results were all great!
Then I tried to implement these test classes into my swing-based applications. So I want to call these same functions, as in the test classes, as a result of any user action (for example, selecting the asio driver in a combobox) But then these asio driver functions just stop to work. I get errors saying that the ASIO driver is not available. (meaning that the dll wrapper loads the wrong asio driver or can't load one at all)
The library path and classpath are all set correctly, exactly the same as the test classes. Even copied the test code word for word in to my swing applications but it still will not work. I am calling these functions in a new Thread, and even put them in a static methods to try and get that working. When calling these asio methods from the main() method AFTER I set up my components gives me the desired results as well. But as soon as I call these same methods (which are in the same class) from a swing event, it fails;
public class ASIOTest
     public static void main(String[] args)
          ASIOTest test = new ASIOTest();
          test.callFunction(); // <-- WORKS
     public ASIOTest()
          initializeComponents();
     private void initializeComponents()
          frame = new JFrame();
          choices = new JComboBox();
          choices.addActionListener(new ActionListener() {
            public void actionPerformed(ActionEvent event)
                 // user made selection
                new Thread(
                        new Runnable() {
                            public void run() {
                                try
                                     callFunction(); // <-- DOES NOT WORK
                                catch (Exception e)
                                    e.printStackTrace();
                        }).start();
     public void callFunction()
          initASIO();
          openASIOLine();
}Is there something fundamental I am missing here?
For what reasons can an application which uses JNI functions go wrong when working in a swing enviroment? (and out of a static context, although this does not seem to make any difference, eg. when calling these functions from static methods inside another class, inside a new thread when the user has generated an event)
I am hoping someone could point me in the right direction :-)
Thank you in advance,
Steven
Edited by: dekoffie on Apr 21, 2009 11:11 AM
Edited by: dekoffie on Apr 21, 2009 11:16 AM

Answer 1

jschell wrote:
Two applications.
And you probably run them two different ways.
The environment is different so one works and the other doesn't.Thank you for your fast reply!
Well, I am running the "updated" version from the same environment; I copied the jframe, and a jcombobox into my original test class which only ran in the java console. Consider my second code example in my original post as the "updated" version of the first code example. And as I pointed out, it works fine when I call the jni functions in the main method, but not when I call it from inside the ActionListener.
Or am I again missing something essential by what you mean with a different environment? The classpath and the working directory is exactly the same, as is the Djava.library.path option. :-)
Thanks again!