Hi, I have a requirement where I need to use a third party tool for a specific business purpose. The tool provides a Java API, but uses JNI. The EJB spec says native class shud be avoided. Is there a way by which this can be done? Thanks in asvance, Best Wishes Shyam
posted 14 years ago
We've done a similar thing with a third party windows dll which we needed to integrate in our J2EE project. We wrapped the DLL with JNI and run this as a simple RMI service on it's own machine. Then the EJB has to call this module via RMI as a client. Then you are clean according to the EJB spec, your code is still portable, all you need is a small extra windows machine with this RMI service running. Ok, there is a little bit overhead to this solution, but then you are more loosly coupled to this third party module.