Updates and revisions

This guide includes the following documentation and code sample changes.

Note   If you are upgrading from version 7.3.1 or earlier, and have developed custom filters, you must update your custom filter classes and recompile before upgrading. For more details, see the changes to classes described in Changes in version 7.4.0.

Changes in version 7.6.2

Changes in version 7.6.1

No changes.

Changes in version 7.6.0

  • Removed references to API Gateway Analytics.

Changes in version 7.5.3

  • Added information on the CheckboxGroupAttribute element to the Declarative UI reference. For details, see CheckboxGroupAttribute.
  • Updated or removed information on the jabber and restJabber code samples as these samples are no longer included in the code samples supplied with API Gateway.

Changes in version 7.5.2

  • Replaced links to the API Gateway REST API documentation on Axway Support at https://support.axway.com with links to the the Axway Documentation portal at https://docs.axway.com where the API Gateway REST API documentation is now available in Swagger format.

Changes in version 7.5.1

  • The following API documentation has been removed from the API Gateway installation.
    • apidocs – Documentation for the REST APIs provided by API Gateway.
    • javadoc – Javadoc for the API Gateway classes.
  • This documentation is now available online:

Changes in version 7.4.2

  • All sections in this guide were updated to reflect changes to the tree structure in Policy Studio.

Changes in version 7.4.1

  • API Gateway is now built on JDK 1.8. As a result, the samples should also be built with JDK 1.8. For more details, see Build the code samples.
  • Code samples in the guide were updated with the class changes that occurred in 7.4.0 (see Changes in version 7.4.0).
  • Many classes changed to new packages and were moved to new JAR files and directories. Several of the JAR files were relocated to new directories in API Gateway and Policy Studio. To pick up the correct JARs and classes, ensure that you build against the latest CLASSPATH paths as defined in the build.xml files in the SDK samples. The JAR file naming convention is: informative-name.version.(in some cases)version-qualifier.
  • The location of the Policy Studio help files for custom filters has changed. For more details, see Create the Policy Studio classes. Ensure that your local build.xml file for the code samples is updated with the latest SDK changes and that the CLASSPATH is correct.

Changes in version 7.4.0

  • The developer samples in the INSTALL_DIR/apigateway/samples/developer_guide directory were updated with the following changes:
    • The PropDef class changed location from com.vordel.circuit.PropDef to com.vordel.common.util.PropDef.
    • The Circuit class changed location from com.vordel.circuit.Circuit to com.vordel.config.Circuit.
    • The SolutionPack class is replaced with ConfigContext in method signatures. For example, any uses of com.vordel.precipitate.SolutionPack are changed to com.vordel.config.ConfigContext.
    • The LoadableModule class changed location from com.vordel.dwe.LoadableModule to com.vordel.config.LoadableModule.
    • The test ClientResponse class changed from com.sun.jersey.api.client.ClientResponse to javax.ws.rs.core.Response.
    • The packages imported and used in the RestJabberRequestClient Test class have changed.
  • You must recompile the classes.

Related Links