Can WBI plugins use native code like other Java programs?
Yes. Because WBI is written in Java, WBI plugins can use native code through the Java Native Interface (JNI). The example History plugin does this. Native code should reside in special subdirectories. We provide a method Proxy.getNativePath() that allows you to write platform independent Java code for loading native libraries. The idea is to separate native code into platform dependent subdirectories. The names of these directories reflect the operating systems and architectures that the native code was compiled for. The names can be determined by a Java program at runtime. See Proxy.getNativePath() for details. • What are some useful packages and classes in WBI? The com.ibm.wbi.http.beans package contains many useful MEG classes that you can extend or use as is. The DocumentInfo class is helpful for getting information about HTTP requests and responses. DocumentInfo instances are obtained by calling getRequestInfo on a RequestEvent and casting the result to a DocumentInfo.
Yes. Because WBI is written in Java, WBI plugins can use native code through the Java Native Interface (JNI). The example History plugin does this. Native code should reside in special subdirectories. We provide a method Proxy.getNativePath() that allows you to write platform independent Java code for loading native libraries. The idea is to separate native code into platform dependent subdirectories. The names of these directories reflect the operating systems and architectures that the native code was compiled for. The names can be determined by a Java program at runtime. See Proxy.getNativePath() for details. • What are some useful packages and classes in WBI? The com.ibm.wbi.http.beans package contains many useful MEG classes that you can extend or use as is. The DocumentInfo class is helpful for getting information about HTTP requests and responses. DocumentInfo instances are obtained by calling getRequestInfo on a RequestEvent and casting the result to a DocumentInfo. When writin
