Java calls IDL for error handling, java calls idl

Java calls IDL for error handling, java calls idl

In the past, we have a detailed introduction to calling idl in java (javaidlb. jar )].

 

Later I found that some errors may occur when different people load javaidlb. jar in different ways.

 

Method 1: load (C: \ Program Files \ Exelis \ IDL82 \ resource \ bridges \ export \ java \ javaidlb. jar ).

The second method is to copy javaidlb. jar to the project.

 

The first method is recommended.

Because the second method may cause some errors, the console will report the following error information:
Failed to load idl_ebutil from F: \ MyEclipse \ testapp \ jar \... \ .. \ bin. x86
Failed to load idl_ebutil from F: \ MyEclipse \ testapp \ jar \... \ .. \ bin. x86
Failed to load idl_bml from default location.
Failed to load javaidlb from default location.
Exception in thread "Timer-0" java. lang. UnsatisfiedLinkError: com. idl. javaidl. JIDLPAL. nativeInitJPAL () V
At com. idl. javaidl. JIDLPAL. nativeInitJPAL (Native Method)
At com. idl. javaidl. JIDLPAL. <clinit> (JIDLPAL. java: 206)
At com. idl. javaidl. JIDLObject. <init> (JIDLObject. java: 56)
At com. idl. javaidl. java_IDL_connect. <init> (java_IDL_connect.java: 30)
At com. zkyg. action. MetadaHarvestAction. list (MetadaHarvestAction. java: 108)
At com. zkyg. action. MetadaHarvestAction $ MyTask. run (MetadaHarvestAction. java: 329)
At java. util. TimerThread. mainLoop (Timer. java: 512)
At java. util. TimerThread. run (Timer. java: 462)

 

No solution has been found for this problem, so the first loading method is used if errors are not avoided.