Comments on: JNI and I - Krapf looks at .NET-J2EE interop http://tssblog.blogs.techtarget.com/2007/07/18/jni-and-i-krapf-looks-at-net-j2ee-interop/ Sat, 07 Nov 2009 19:05:51 +0000 http://wordpress.org/?v=wordpress-mu-1.0 by: Steve Channell http://tssblog.blogs.techtarget.com/2007/07/18/jni-and-i-krapf-looks-at-net-j2ee-interop/#comment-488 Thu, 19 Jul 2007 13:35:08 +0000 http://tssblog.blogs.techtarget.com/2007/07/18/jni-and-i-krapf-looks-at-net-j2ee-interop/#comment-488 What we need in the Java world is a higher level interoperability technology that enables us to reference binary components without having to write low-level C functions to bridge the gap between Java classes and C++ (or other language) binary classes. It would be really neat if the JVM included a binding to Bonobo for Gnone, so that Java classes could simply declare an import attribute (to reference the “.so”) and have the compiler generate the mapping to code. In the binary world, you’d develop Bonobo components using high-level tools. I guess you’d really want the interface to be agnostic between Bonono and XPCOM so that you’d also be able to integrate in the Mozilla world. Heck, if your interface is agnostic between Bonobo & XPCOM, you’d probably want to cover COM on windows as well. Hey, here is the solution: 1) Create a JVM interop binding for binary component interop. 2) Create a platform specific implementation that uses COM, XPCOM or Bonobo 3) Add an import attribute to the Java language and extend the compiler. Why, oh why has nobody thought of it yet? .. oh yes, silly me.. isn’t that was Microsoft did and didn’t Sun sue to them for it. “If you like burning bridges.. you should learn to live on an Island” What we need in the Java world is a higher level interoperability technology that enables us to reference binary components without having to write low-level C functions to bridge the gap between Java classes and C++ (or other language) binary classes.

It would be really neat if the JVM included a binding to Bonobo for Gnone, so that Java classes could simply declare an import attribute (to reference the “.so”) and have the compiler generate the mapping to code. In the binary world, you’d develop Bonobo components using high-level tools.

I guess you’d really want the interface to be agnostic between Bonono and XPCOM so that you’d also be able to integrate in the Mozilla world. Heck, if your interface is agnostic between Bonobo & XPCOM, you’d probably want to cover COM on windows as well.

Hey, here is the solution:

1) Create a JVM interop binding for binary component interop.
2) Create a platform specific implementation that uses COM, XPCOM or Bonobo
3) Add an import attribute to the Java language and extend the compiler.

Why, oh why has nobody thought of it yet?

.. oh yes, silly me.. isn’t that was Microsoft did and didn’t Sun sue to them for it.

“If you like burning bridges.. you should learn to live on an Island”

]]>