latest news


j-Interop 2.08 Released.

read more ...


j-Interop 2.07 Released.

read more at sourceforge


  • W.O.R.A: True platform independance

    Since j-Interop is implemented in pure Java and does not use JNI , it can be hosted from any platform (Unix,Mac,Solaris...) and is not restricted to Windows.
  • Clean integration of two of the leading technologies without writing any native code

    j-Interop eliminates any need to write native (JNI) DLLs, decreasing development time and shortening the entire software lifecycle for the products (based on j-Interop). Such products are also saved from any kind of instability in function resulting from poorly written native code (DLLs).
  • Accessing COM components from any type of Java client, including Applets, EJBs, Servlets, JSPs, and standalone applications

    Since it is pure Java, j-Interop can be used within any J2EE server, on any platform (which supports Java).
  • Maximizing reuse of existing Java and COM components

    All the plumbing on interoperating with COM servers is done by j-Interop, it makes reusing same components again, instead of porting back and forth between domains, a more lucrative and viable option.
  • No longer should there be a dependency on cross platform resources thus minimizing cost and improving quality

    The same resources for Java can be utilized without any additional training\competency building and the turn around time can be bought down substantially. Not having to deal with native code also removes the complexity associated with maintaining the same. The code is now much cleaner and has a distinct segregation between what is from one domain and what is from another. Debugging the projects based on j-Interop is substantially easier than debugging JNI based DLL projects.
  • Easier deployment, there is no custom code at the server

    There has to be no special treatment given to j-Interop clients, they just behave like standard DCOM clients. This is a big advantage in terms of administering the machines where the COM servers are deployed. The administrator does not have to care about security or the instability of the native components bringing the server down (Denial of Service).
  • Increasing marketability of products across domains

    Choice of low turn around time, easier deployment, no requirement of cross platform resources, less maintainability all scale up the availability and marketability of products (based on j-Interop) across domains.