🚀 go-pugleaf

Kevin,

I am having a similar problem. I have done what you suggested below, adding
the -Djava.library.path=  to the location of the .DLL. It seems more like it
cannot find the function inside the DLL as opposed to the DLL itself as
before I copied the DLL to that location, the error described the DLL name
instead of the funciton. I wrote a test DLL and was able to call it from
Delphi, so I know the methods are public and exported properly. However,
when I run from java, I get the same error as yc did. Here is my code and
error:

public class DLLBridge
{
    public DLLBridge() {
    }
    public native void RprtMain();

    static{
        System.loadLibrary("Reports");
    }

    public static void main(String[] args) {
        DLLBridge dbridge = new DLLBridge();
        dbridge.RprtMain();
    }
}

java.lang.UnsatisfiedLinkError: RprtMain
 at com.util.DLLBridge.RprtMain(Native Method)
 at com.util.DLLBridge.main(DLLBridge.java:21)
Exception in thread "main"

Is there something I'm missing? Thanks in advance,
Chris

"Kevin Dean [TeamB]" <NkOdSePaAnM@datadevelopment.com> wrote in message
news:xn0dyx2iu419bb001-kdean@www.teamb.com...
> yc wrote:
>
> >
> > Hi,
> > I have a c dll (MyDll) stdcall fnc as follows.
> > stdcall int MyFnc(int FileNo, int IOType, unsigned char *
> > DataToWrite, unsigned char *  DataRead);
> >
> > I try to call from java code, but it gives me an error as follows.
> >
> > Exception in thread "main" java.lang.UnsatisfiedLinkError: Myfunc
> >         at X.MyFnc(Native Method)
> >         at X.main(X.java:6)
> >
>
> That means that the Java process can't find the DLL in the system path.
> Make sure that you add the appropriate directory to the PATH statement
> or add -Djava.library.path=<dll_location> to the command line.
>
> -- 
> Kevin Dean [TeamB]
> Dolphin Data Development Ltd.
> http://www.datadevelopment.com/
>
> NEW WHITEPAPERS
> Team Development with JBuilder and Borland Enterprise Server
> Securing Borland Enterprise Server
> http://www.datadevelopment.com/papers/index.html
>
> Please see Borland's newsgroup guidelines at
> http://info.borland.com/newsgroups/guide.html