This release has been compiled and tested with Oracle Java 1.6u43.

The following changes have been made across all Java API Jar files where applicable.

A new method, AgCore_JNI.xInitThreads(), has been added to the API. This method must be called on Linux before any other calls to x11 are made.

New event has been added, onConControlQuitRecieved, that is triggered when the [ConControl / QuitStk] connect command is received.

Changes have been made to the this API, please refer to STKUtil What's New for changes.

Changes have been made to this API, please refer to STK Object Model What's New for more details. Also refer to the following Java API specific deletions, refactoring, and additions:

Changes have been made to this API, please refer to STK Astrogator What's New for all changes.

Changes have been made to this API, please refer to STK VGT What's New for all changes.

Changes have been made to this API, please refer to STK Graphics What's New for changes.

This release has been compiled and tested with Oracle Java 1.6u43.

The following changes have been made across all Java API Jar files where applicable.

A new method, AgCore_JNI.xInitThreads(), has been added to the API. This method must be called on Linux before any other calls to x11 are made.

New classes and interfaces have been added to support Cesium terrain in STK Engine. EX: AgStkGraphicsAGICustomTerrainOverlayClass

New event has been added, onConControlQuitRecieved, that is triggered when the [ConControl / QuitStk] connect command is received.

Changes have been made to the this API, please refer to STKUtil What's New for changes.

Changes have been made to the this API, please refer to STKX What's New for changes. Also the following Java API specific deletions, refactoring, and additions:

Changes have been made to this API, please refer to STK Object Model What's New for more details. Also refer to the following Java API specific deletions, refactoring, and additions:

Changes have been made to this API, please refer to STK Astrogator What's New for all changes.

Changes have been made to this API, please refer to STK VGT What's New for all changes.

Changes have been made to this API, please refer to STK Graphics What's New for changes.

Changes have been made to this API, please refer to STK Ui Core What's New for all changes.

Changes have been made to this API, please refer to STK Ui Application What's New for all changes.

The following changes have been made across all Java API Jar files where applicable.

The Java samples have been greatly improved and refactored. A few have been removed, but many more have been added or updated to display new features that have been added to the STK Java API and STK 10.0 release. Please refer to Custom Application Java Samples, Automation Application Java Samples, and Plugin/Extension Application Java Samples

The STK Java API javadocs jar file name has been renamed from agi.javadocs.jar to agi.stk.javadocs.jar

Changes have been made to the this API that include the following deletions and additions:

Changes have been made to the this API that include the following deletions, refactoring, and additions:

Types previously contained in this package have been repackaged to the agi.core.swing.jar library, additionally:

Types previously contained in this package have been repackaged to the agi.core.swt.jar library.

Changes have been made to the this API. Please refer to STKUtil What's New for changes.

Changes have been made to the this API. Please refer to STKX What's New for changes. Also the following Java API specific deletions, refactoring, and additions:

This jar library provides the AWT based Globe, Map, and Gfx Analysis Controls as well as Swing based JPanel wrappers for each to ease hosting the AWT controls within Swing containers. This jar library is to be included in applications that utilize the AWT/Swing framework for their UI.

This jar library provides the SWT based Globe, Map, and Gfx Analysis Controls. This jar library is to be included in applications that utilize the SWT framework for their UI.

This jar library provides the future initialization help for STKX based applications.

Changes have been made to the this API, please refer to STK Object Model What's New for more details. Also refer to the following Java API specific deletions, refactoring, and additions:

Changes have been made to the this API, please refer to STK Astrogator What's New for all changes.

Changes have been made to the this API, please refer to STK VGT What's New for all changes.

This new library has been added to provide advanced graphics manipulation within a 3d/Globe control's scene. Refer to STK Graphics What's New for changes.

Note: If used this will cause compilation/runtime breakage.

agi.stk.jar has been removed from the release. All types previously contained within this jar file have been moved to new jar files as the following table indicates. The initialization/uninitialization for such applications was moved to this Jar to remove some circular dependencies that inhibited the API from moving forward toward the best possible design.

Use agi.stk.ui.AgStkUi class instead of previous agi.stk.AgStk class. Methods have changed names slightly as well, see STK Automation samples for examples.

agi.stk.AgStk_JNI has been removed in favor of new initialization/uninitialization strategy for 10.0

This jar library provides the AgStkAutomation_JNI initialization class used to initialize/uninitialize Automation Application types in AWT/Swing or SWT.

Changes have been made to the this API, please refer to STK Ui Core What's New for all changes.

Changes have been made to the this API, please refer to STK Ui Application What's New for all changes.

Note: If used this will cause compilation/runtime breakage.

The AGI Java Plugins for STK have been refactored into new packages/new jars/new dlls as seen in the list below.

This jar library has been added to provide AgStkExtension_JNI class used to initialize/uninitialize Extension/Plugin Application types. Note this class should be used by the STK UI application and is not intended to be access via a customer applications. The initialization/uninitialization for such applications was moved to this Jar to remove some circular dependencies that inhibited the API from moving forward toward the best possible design.

This new library has been added to provide advanced graphics manipulation plugin points for end user custom Raster and Projection Stream graphics within a 3d/Globe control's scene. Refer to STK Graphics Plugins

This jar library and its API are released as PRE-ALPHA in STK 10.0 and are subject to change in future releases. This library has been added to the SDK to help with general AWT/Swing related integration. Specifically:

This jar library and its API are released as PRE-ALPHA in STK 10.0 and are subject to change in future releases. While it is configured, used (as well as some of its classes/interfaces/etc directly or indirectly) within some samples, it and its classes/interfaces/etc are not required to be used or packaged within your final application.

This jar library and its API are released as PRE-ALPHA in STK 10.0 and are subject to change in future releases. While it is configured, used (as well as some of its classes/interfaces/etc directly or indirectly) within some samples, it and its classes/interfaces/etc are not required to be used or packaged within your final application.

This jar library and its API are released as PRE-ALPHA in STK 10.0 and are subject to change in future releases. While it is configured, used (as well as some of its classes/interfaces/etc directly or indirectly) within some samples, it and its classes/interfaces/etc are not required to be used or packaged within your final application.

This jar library and its API are released as PRE-ALPHA in STK 10.0 and are subject to change in future releases. While it is configured, used (as well as some of its classes/interfaces/etc directly or indirectly) within some samples, it and its classes/interfaces/etc are not required to be used or packaged within your final application. It provides some non-UI code that is utilized within the agi.stk.core.swing.jar and agi.stk.core.swt.jar.

This jar library and its API are released as PRE-ALPHA in STK 10.0 and are subject to change in future releases. While it is configured, used (as well as some of its classes/interfaces/etc directly or indirectly) within some samples, it and its classes/interfaces/etc are not required to be used or packaged within your final application. It provides some UI components that can be used in Custom or Automation applications based on AWT/Swing such as Animation Toolbars, View Toolbars, etc.

This jar library and its API are released as PRE-ALPHA in STK 10.0 and are subject to change in future releases. While it is configured, used (as well as some of its classes/interfaces/etc directly or indirectly) within some samples, it and its classes/interfaces/etc are not required to be used or packaged within your final application. It provides some UI components that can be used in Custom or Automation applications based on SWT such as Animation Toolbars, View Toolbars, etc.

This jar library provides the AgStkCustomApplication_JNI initialization class used to initialize/uninitialize Custom Application types in AWT/Swing or SWT. The initialization/uninitialization for such applications was moved to this Jar to remove some circular dependencies that inhibited the API from moving forward toward the best possible design.

This jar library and its API are released as PRE-ALPHA in STK 10.0 and are subject to change in future releases. While it is configured, used (as well as some of its classes/interfaces/etc directly or indirectly) within some samples, it and its classes/interfaces/etc are not required to be used or packaged within your final application. It provides some High-level UI Native Application infrastructure to ease application development with Custom applications based on AWT/Swing.

The STK Java API implements all the new/changed/removed interfaces/classes/enumerations/methods that are provided in the STKUtil, STKX, STK Object Model, STK Astrogator APIs. For further details please refer to the 'What Is New' pages for STKUtil, STKX, STK Object Model, STK Astrogator and STK VGT.

The STK Java API now provides an Object Oriented API to AGI's Vector Geometry Tool feature within STK and STK Engine.

To use this new API you must include the agi.stkvgt.jar and AgJNIStkVGT.dll / libagjnistkvgt.so library in your configuration settings.

Please refer to the STK Java API Custom Application Java Samples, and locate the VGT Basic sample.

The STK Java API default initialization and uninitialization strategy now also initialize/uninitialize the STK Vector Geometry Tool API jar file in addition to the previous release jar files. This unfortunately breaks backward compatibility at runtime for the default initialization and uninitialization strategy, but consequentially adds a new feature in the form of the Vector Geometry Tool API to the STK Java API.

Thus if you are using one of the standard initialization/uninitialization strategies you will be required to add the VGT jar / jni libraries to your configuration settings or you will experience a java.lang.NoClassDefFoundError or java.lang.UnsatisfiedLinkError.

If you are unable to add the VGT jar / jni libraries to your configuration settings then you can initialize/uninitialize the STK Java API without the VGT API. Please contact AGI Technical Support if more help is needed.

The STK Java API implements all the new/changed/removed interfaces/classes/enumerations/methods that are provided in the STKUtil, STKX, STK Object Model, STK Astrogator APIs. For further details please refer to the 'What Is New' pages for STKUtil, STKX, STK Object Model and STK Astrogator.

State of the control's scene has been maintained across add/remove from a parent container during dock, minimize, maximize type UI operations. Please refer to the STK Engine blog post pertaining to this discussion.

The FAQ has been updated with information regarding Object Model hierarchy navigation.

The STK Java API implements all the new/changed/removed interfaces/classes/enumerations/methods that are provided in the STKUtil, STKX, STK Object Model, STK Astrogator APIs. For further details please refer to the 'What Is New' pages for STKUtil, STKX, STK Object Model and STK Astrogator.

The agi.logging and agi.util packages are now compiled into the agi.jar binary file. Thus the agi.logging.jar and agi.util.jar binary files NO LONGER EXIST as part of the STK Java API 9.1 installation.

The APIs in the agi.logging and agi.util packages are still accessible as in previous releases thus preserving code backward compatibility.

However, the development and runtime configuration setup is no longer backward compatible. It will be necessary to remove the agi.logging.jar and agi.util.jar from your configuration setup.

The STK Java API has deprecated the default initialization and uninitialization strategy in favor of an "Application Type" initialization approach.

Please contact AGI Technical Support if more help is needed.

The STK Java API now provides an Object Oriented API to AGI's STK User Interface Core/Application automation feature. This feature allows one to automate the STK product from Java. This feature is currently available on windows platforms only.

To use this new API you must include the agi.stk.ui.core.jar and AgJNIStkUiCore.dll library as well as agi.stk.ui.application.jar and AgJNIStkUiApplication.dll library in your configuration settings.

Note: This API replaces the agi.stk.jar and AgJNIStk.dll implementation. For differences in the new API see the change regarding deprecation of agi.stk.jar below

In order to make the STK Automation feature within the STK Java API standard by using the AGI STK User Interface API, some methods had to be changed causing a compilation error and breaking backward compatibility. Notably...

• Library deprecation
  
  

  Deprecated/Old	Preferred/New
  AgJNIStk.dll(no longer shipped)	AgJNIStkUiCore.dll and AgJNIStkUiApplication.dll

• 
  
• Deprecation/Changes within agi.stk.AgStk class

  You will encounter the following backward compatibility breaking compilation errors:

  
  

  Deprecated/Old	Preferred/New
  public long getHeight()	public int getHeight()
  public void setHeight(long)	public void setHeight(int)
  public long getWidth()	public int getWidth()
  public void setWidth(long)	public void setWidth(int)
  public long getTop()	public int getTop()
  public void setTop(long)	public void setTop(int)
  public long getLeft()	public int getLeft()
  public void setLeft(long)	public void setLeft(int)
  public void startLaunchPad()	Removed. Launch Pad is no longer supported
  public static void releaseStkInstance()	Removed. Use the AgStk instance release() method instead.
  public static AgStk createStkInstance()	Removed. Use the AgStk default constructor instead.
  public static AgStk createStkInstance(String progid)	Removed. Use the AgStk default constructor instead.
  public static AgStk getStkInstance(String progid)	Removed. Use public static AgStk getStkInstance()

  
  

  Deprecation of agi.stk.AgStk_JNI class

  The entire class of agi.stk.AgStk_JNI has been deprecated in favor of reuse of the agi.ui.core.AgUiCore_JNI and agi.ui.application.AgUiApplication_JNI. The agi.stk.AgStk_JNI class can still be used but it is preferred that deprecated/old code be changed to the preferred/new code as follows:

  
  

  Deprecated/Old	Preferred/New
  agi.stk.AgStk_JNI.load()	None. This should not be used/called and is no longer necessary/accessible.
  agi.stk.AgStk_JNI.initialize()	Use agi.stk.ui.core.AgStkUiCore_JNI.initialize() and agi.stk.ui.application.AgStkUiApplication_JNI.initialize() instead.
  agi.stk.AgStk_JNI.uninitialize()	Use agi.stk.ui.core.AgStkUiCore_JNI.uninitialize() and agi.stk.ui.application.AgStkUiApplication_JNI.uninitialize() instead.

  
  

The STK Java API now provides the STK Access Constraint Plugin API feature. This feature allows one to write an STK Access Constraint Plugin to provide custom Access Constraint computations in Java. This allows our customers to create an Access Constraint Plugin based on their pre-existing non-STK Java Access Constraint code base.

To use this new API you must create a plugin in accordance with the AGI Access Constraint Plugin Java standards.

An online article with more details can be found on the STK Engine Blog

Please refer to the STK Java API javadocs for specifics on the API class/method deprecation.

The STK Java API implements all the new/changed/removed interfaces/classes/enumerations/methods that are provided in the STKUtil, STKX and STK Object Model APIs. For further details please refer to the 'What Is New' pages for STKUtil, STKX, and STK Object Model.

The STK Java API now provides an Object Oriented API to AGI's Astrogator Propagator feature within STK and STK Engine.

To use this new API you must include the agi.stkobjects.astrogator.jar and AgJNIStkGator.dll / libagjnistkgator.so library in your configuration settings.

Please refer to the STK Java API Custom Application Java Samples, and locate the CustomApplication_Astrogator_MarsProbe sample.

The STK Java API default initialization and uninitialization strategy now also initialize/uninitialize the Astrogator API jar file in addition to the previous release jar files. This unfortunately breaks backward compatibility at runtime for the default initialization and uninitialization strategy, but consequentially adds a new feature in the form of the Astrogator propagation API to the STK Java API.

Thus if you are using one of the standard initialization/uninitialization strategies you will be required to add the Astrogator jar / jni libraries to your to your configuration settings or you will experience a java.lang.NoClassDefFoundError or java.lang.UnsatisfiedLinkError.

If you are unable to add the Astrogator jar / jni libraries to your configuration settings then you can initialize/uninitialize the STK Java API without the Astrogator API. Please contact AGI Technical Support if more help is needed.

The following STK Java API AWT based classes/controls/methods have been deprecated, though will still be useable for backward compatibility reasons.

Specifically...

Please refer to the STK Java API javadocs for specifics on the API class/method deprecation.

Even though the above classes are deprecated, they will still function as expected to respect backward compatibility because they are derived or are composed of the new repackaged/renamed components in the agi.core.awt and agi.stkx.awt packaged classes.

Specifically ...

• The agi.core.Ag_JNI class now is composed of the agi.core.awt.AgAwt_JNI class
  
  Note: Backward compatibility is still supported using the agi.core.Ag_JNI class initialize/uninitialize methods, in detail ...
  
  
  • The agi.core.Ag_JNI.initialize() calls the agi.core.awt.AgAwt_JNI.initialize() method.
  • 
    
  • The agi.core.Ag_JNI.uninitialize() calls the agi.core.awt.AgAwt_JNI.uninitialize() method.
  • 
    
  • The agi.core.Ag_JNI.isInitialized() calls the agi.core.awt.AgAwt_JNI.isInitialized() method.
  • 
    
  • The agi.core.Ag_JNI.isOnUnixPlatform() calls the agi.core.awt.AgAwt_JNI.isOnUnixPlatform() method.
  • 
    
• 
  
• The agi.stkx.AgUiAxVOCntrl class now derives from agi.stkx.awt.AgGlobeCntrlClass
• The agi.stkx.AgUiAx2DCntrl class now derives from agi.stkx.awt.AgMapCntrlClass
• The agi.stkx.AgUiGfxAnalysisCntrl class now derives from agi.stkx.awt.AgGfxAnalysisCntrlClass

New AWT based applications should adhere to the following API guidelines in favor of the above mentioned deprecated classes/methods:

• Should import and use the agi.core.awt and agi.stkx.awt packages in addition to agi.core and agi.stkx packages.
• 
  
  
• Should initialize/uninitialize the STK Java API using ...
  
  
  • To initialize call the agi.core.awt.AgAwt_JNI.initialize() method.
  • 
    
  • To uninitialize call the agi.core.awt.AgAwt_JNI.uninitialize() method.
  • 
    
• 
  
• Should integrate STK's Globe, Map, GfxAnalysis controls by using ...
  
  
  • agi.stkx.awt.AgGlobeCntrlClass
  • 
    
  • agi.stkx.awt.AgMapCntrlClass
  • 
    
  • agi.stkx.awt.AgGfxAnalysisCntrlClass
  • 
    

The impetus for the repackaging/renaming of these graphical components/widgets was two part:

• To provide a simpler/clearer name for these graphical components.
• To provide a packaging scheme that allowed reuse of the non-graphical interfaces and classes from either the AWT based graphical components (agi.stkx.awt package) or the new SWT based graphical widgets (agi.stkx.swt package) which is a new feature released in STK 9.0 (see next feature entry Standard Widget Toolkit (SWT) framework implementation).

Please note if your Java application was previously written using AWT framework and used the agi.core classes and the agi.stkx controls, your application should continue to work without changing to the equivalent agi.core.awt classes and agi.stkx.awt controls.

Please refer to the STK Java API samples page for details on how to use these new backward compatible code changes.

The STK Java API now provides a native windowing framework implementation for SWT allowing our customers to write pure SWT Java applications.

Further, the new packages of agi.core and agi.stkx have been split to accommodate both the AWT and SWT windowing frameworks. The AWT windowing framework guidelines are listed in the previous feature entry entitled Abstract Window Toolkit (AWT) component repackaging/renaming for Globe/Map/GfxAnalysis components.

Applications built using the SWT windowing framework should adhere to the following guidelines:

• Should import and use the agi.core.swt and agi.stkx.swt packages in addition to agi.core and agi.stkx packages.
• 
  
  
• Should initialize/uninitialize the STK Java API using ...
  
  
  • To initialize call the agi.core.swt.AgSwt_JNI.initialize() method.
  • 
    
  • To uninitialize call the agi.core.swt.AgSwt_JNI.uninitialize() method.
  • 
    
• 
  
• Should integrate STK's Globe, Map, GfxAnalysis controls by using ...
  
  
  • agi.stkx.swt.AgGlobeCntrlClass
  • 
    
  • agi.stkx.swt.AgMapCntrlClass
  • 
    
  • agi.stkx.swt.AgGfxAnalysisCntrlClass
  • 
    

Please refer to the STK Java API SWT based applications on the samples page. Specifically, the SWT samples are titled "SwtAgiCanvas" and "SwtAgiCanvasEclipsePlugin".

The setPicture/getPicture methods in the STK Java API's controls(all Globe/Map/GfxAnalysis classes/interfaces) for both the AWT and SWT implementation have now been deprecated in favor of "setPictureFromFile" and "getPictureFromFile" methods. The setPicture/getPicture methods will continue to function for backward compatibility and internal call the getPictureFromFile and setPictureFromFile methods. The class's that contain these deprecated methods are ...

• agi.stkx.AgUiAxVOCntrl
• agi.stkx.IAgUiAxVOCntrl
• agi.stkx.AgUiAx2DCntrl
• agi.stkx.IAgUiAx2DCntrl
• agi.stkx.AgUiAxGfxAnalysisCntrl
• agi.stkx.IAgUiAxGfxAnalysisCntrl
• agi.stkx.AgGlobeCntrl
• agi.stkx.AgMapCntrl
• agi.stkx.AgGfxAnalysisCntrl
• agi.stkx.awt.AgGlobeCntrlClass
• agi.stkx.awt.AgMapCntrlClass
• agi.stkx.awt.AgGfxAnalysisCntrlClass
• agi.stkx.swt.AgGlobeCntrlClass
• agi.stkx.swt.AgMapCntrlClass
• agi.stkx.swt.AgGfxAnalysisCntrlClass

Please refer to the STK Java API javadocs for specifics on the API class/method deprecation.

The various Globe/VO, Map/2D, and GfxAnalysis classes/interfaces have been redesigned for 9.0, but are still backward compatible for previous releases. The following is a quick explanation for each ...

Please refer to the STK Java API javadocs for specifics on the API class/method deprecation.

The AgSafeArray has deprecated some methods related to iterating through multidimensional arrays (i.e. getDimUpperBound(), getDimLowerBound(), getDimLength(), etc.), see the STK Java API javadocs deprecation flags on the agi.core.AgSafeArray class for details. Instead use getRowCount() and getColumnCount() as indicated in the STK Java API javadocs provided in the agi.javadocs.jar file.

Note: Effort has been taken to attempt to provide backward compatibility, however, some data returned in Multidimensional arrays may be returned in new element ordinals that are more accurate.

Please refer to the STK Java API javadocs for specifics on the API class/method deprecation.

The STK Java API is officially released on the Windows operating systems. Previously the STK Java API was only available with STK Engine for Unix (4DX on Unix) releases 6.1.3, 7.0.1, and 8.0.2.