devNote d061101  info.odma.odmjni100 Java-OdmNative Bridge 0.58 beta Runtime Packaging

ODMdev>devNotes> 2006>11> d061101n> 0.05 2008-04-23 21:12 -0700

• Latest version: The latest info.odma.odmjni100 material can be found via   <http://ODMA.info/dev/devNotes/2006/11/d061101b.htm>.

  visits to popular ODMdev pages

• Previous version: 0.58beta Runtime Packaging <http://ODMA.info/dev/devNotes/2006/11/d061101m.htm>.
    
• Next odmjni100 version: 0.59 beta Transition Candidate <http://ODMA.info/dev/devNotes/2006/11/d061101o.htm>.
• Next Runtime Packaging version: ODMJNI 1.0 Public Beta 0.59 Transition Packaging <http://ODMA.info/dev/devNotes/2007/09/d070901c.htm>
           
• This version:  0.05 Runtime Packaging: 0.58beta <http://ODMA.info/dev/devNotes/2006/11/d061101n.htm>. 
• Downloads:
  • d061101n.txt: 0.00 13,983 byte file dated 2007-04-10-23:15, Manifest for the d061101n 0.58beta archive
  • d061101n-ODMJNI1.0-0.58beta.zip: 0.00 1,577,087 byte file dated 2007-04-10-23:15.  Review the manifest to determine whether it is worthwhile to download the Zip archive.
  • ODMJNI100-0.58beta.txt:  0.02 12,517 byte file dated 2007-04-10-15:30, narrative manifest of the ODMJNI 1.0 runtime archive
  • ODMJNI100-0.58beta.zip:  0.02 121,739 byte file dated 2007-04-10-15:31 complete runtime package for the 0.58beta release of ODMJNI 1.0

{Author Note: this is a placeholder for the 0.58beta Integration.  There will be code.  Initially, this is also a place for notes created during early stages for items to remember to handle in the 0.58beta update and integration.}

1. Overview

Additional details are found in the manifest file for download of the code and scripts.

Three steps are defined and implemented for simplified deployment of the executable code:

1. The OdmJniBind class is updated to provide for automatic location of Java's awt.dll library.  This library is required for discovery of the GUI application's HWND handle and communication of that handle to the ODMA native code.
   
   This is accomplished by having the Java Runtime Environment always be used directly in initiation of the application so that Windows will look in the JRE bin/ directory for additional DLLs that are called for.
      
   As further streamlining of operation and reduction of the application footprint, the JRE jawt.dll and awt.dll libraries will not be accessed by ODMJNI unless an AWT Window is supplied to the OdmJniBind.application() method.
      
2. Procedures for creating and deploying Java .jar files are added to the development tree.  This allows runtime deployment with easier incorporation in an application's class path and jar structures.
     
   This eliminates the need to deploy the odmjni100.dll to a separate Windows location and library path so long as it is alongside the executable Jar file of the Java application program.
      
3. Elementary regression tests of the deployment package are created.  These confirm correct operation with both the runtime .jar packaging and with the file-system directory class paths. 
     
   The Clicker test application is also incorporated into an executable Java archive for demonstration and confirmation that the runtime is configured properly alongside the application.  The Clicker.jar is distributed as part of the runtime package.

2. Developer Notes: Implementation

2.1 Locating Java's Windows Runtime Libraries

• 2007-03-05: Straightening out awt.dll.  In a customer demo, the Java developer noticed that modal dialogs weren't working, although they work on our development setups.  I wondered if awt.dll was not being found.  There might not be any observed message in the GUI application, and I'm not sure what my code does in that case.  It may also be the case that the jawt.lib code does things to check for the presence of the DLL.
     
  Sergei suggested that I should use a system property to find the DLL, sun.boot.library.path, and use the System.getProperty("sun.boot.library.path") method to get it.
      
• 2007-03-06: Passing the Path to ODMJNI.  I didn't see how that information would help at the native code level.  Then it occurred to me that the path could be passed from OdmJniBind.application(appId, appWindow) to the native getIodmWinNative method so that the DLL can be loaded explicitly in the procedure, freeing it after obtaining the HWND.  Otherwise, the null case should be attempted.
     
• 2007-03-18: Researching the Path Utilities in Java.  I find that there are ways to load libraries or to load arbitrary code.  There are no ways to free libraries, however. 

2.2 Creating Runtime Zip and Jar Files

xxx

2.3 Creating Confirmation Tests for 0.58beta

xxx

Revision History:

0.05 2007-09-25-13:26 Link to the 0.59beta draft

The next version is linked and the continuation of packaging in its own folio is also mentioned.

0.04 2007-04-10-23:29 Include d061101n-ODMJNI1.0-0.58beta.zip Development-Tree Updates

The complete updates to the accumulated 0.50-0.57beta drops are also made available for download.

0.03 2007-04-10-16:32 Include ODMJNI100-0.58beta.zip Runtime

The runtime package is completed and made available for immediate download by the developers.  The complete developer tree source code update and the narrative materials will be provided as a further update.

0.02 2007-03-18-17:14 Redefine 0.58beta

The project is redefined in line with the adjustments that followed introduction and completion of 0.57beta.  This stage is now devoted to developing an initial run-time packaging that can be used separately from the source code and testing development tree.

0.01 2007-03-05-17:54 Modify to reflect introduction of 0.57beta and deferral of full exceptions to here

A more involved exception check is needed for wfDocId and the other cases might as well be handled by shared native implementations too. [update 2007-03-18 This improvement is moved to 0.59beta].

0.00 2007-02-24-19:04 Provide Placeholder for Material

Create placeholder that will be populated with information as the 0.58beta integration is defined and then implemented.

You are navigating ODMdev. This work is licensed under a Creative Commons Attribution 2.5 License.

created 2007-02-24-19:04 -0800 (pst) by orcmid $$Author: Orcmid $ $$Date: 08-04-23 21:12 $ $$Revision: 69 $