Differences

This shows you the differences between two versions of the page.

--- blogtng:2010-06-17:imaris_-_java [2010/06/17 23:05] – kota
+++ blogtng:2010-06-17:imaris_-_java [2020/11/26 09:11] (current) – external edit 127.0.0.1
@@ Line 1: / Line 1: @@
+~~NOTOC~~
 ===== Imaris - Java =====
+Here is some notes on accessing Imaris contents from Java. Since this example uses COM interface via jacob.dll, platform is limited to windows.
 ==== Setup ====
@@ Line 5: / Line 8: @@
 There is a breif description in
 http://www.bitplane.com/go/products/imarisxt
-<quote>
+<blockquote>
 In order to run the JACOB demo, the Java COM Bridge needs to be installed (put the jacob.dll into /bin and the jacob.jar into /lib/ext). The demo does similar things like the demos above: Start Imaris, load a Dataset, perform some action with the image, and terminate Imaris. Many thanks for providing the source code to Volker Bäcker, Monpellier RIO Imaging.
-</quote>
+</blockquote>
 So accessing Imaris from Java requires Jacob pakage (Java - COM Bridge, http://sourceforge.net/projects/jacob-project/). When I downloaded the latest version, two .dll files were included in the package and no jacob.dll.
-<quote>
+<blockquote>
 Jacob.jar relies on a DLL file that it loads off of the library path or classpath. This means that you must either copy the appropriate jacob ddll into your path or use VM options to add directory holding jacob dll to the path. Prior to 1.14M6, the jacob DLL name was alwasy "jacob.dll". This made it hard to verify jacob was loading the correct dll when multiple copies of jacob were installed on a single system. It also was confusing on 64 bit systems where the 32 bit and 64 bit dlls have the same tames. Starting in 1.14M6, Jacob's library loader selects a dll with the appropriate name based on the jacob release and platform. The dll naming convention is:
 jacob<platform>.<version.>.dll
-</quote>
+</blockquote>
 There actually are following two .dll files in the package.