Version 9x release notes

Future Release Candidates

Key Summary T Assignee P Status story points Resolved
Loading...
Refresh

Breaking changes 

  1. NONE

New Features

  1. NONE

Enhancements

  1. NONE

Bug Fixes

  1. NONE

Removed Features

  1. NONE

Known Issues

  1. REP-5531 While the Scripting filter schema indicates support for several languages, the Ruby and Lua implementations have multithreading issues and should not be used in this version of Repose.
  2. REP-6880 Repose will fail to load configuration files with embedded XSLT if the the XSLT Attribute Value Template (AVT, i.e., "{$param}") is used. The reason is that the Repose configuration output template tokens (i.e., "{$env_var$}") clash with the XSLT AVT tokens. The result is that the templating engine attempts to process the AVT (e.g., "{$param}") but cannot find the end of the "code island" (i.e., "$}") and so fails. This issue should only arise if the deprecated feature of embedding XSLT into a configuration file (such as the translation filter configuration) is used, and can be worked around by extracted the XSLT into a file referenced by the configuration file.

Deprecated Features

  1. NONE

Release 9.0.1.0 (TBA)

Key Summary T Assignee P Status story points Resolved
Loading...
Refresh

Breaking changes 

  1. NONE

New Features

  1. NONE

Enhancements

  1. NONE

Bug Fixes

  1. NONE

Removed Features

  1. NONE

Known Issues

  1. REP-5531 While the Scripting filter schema indicates support for several languages, the Ruby and Lua implementations have multithreading issues and should not be used in this version of Repose.
  2. REP-6880 Repose will fail to load configuration files with embedded XSLT if the the XSLT Attribute Value Template (AVT, i.e., "{$param}") is used. The reason is that the Repose configuration output template tokens (i.e., "{$env_var$}") clash with the XSLT AVT tokens. The result is that the templating engine attempts to process the AVT (e.g., "{$param}") but cannot find the end of the "code island" (i.e., "$}") and so fails. This issue should only arise if the deprecated feature of embedding XSLT into a configuration file (such as the translation filter configuration) is used, and can be worked around by extracted the XSLT into a file referenced by the configuration file.

Deprecated Features

  1. NONE

Release 9.0.0.0 (2019-01-31)

Key Summary T Assignee P Status story points Resolved
Loading...
Refresh

Breaking changes 

  1. REP-7009 Updated the intrafilter-logging debugging mechanism in preparation for v9.0.0.0 changes.
    1. See the Troubleshooting guide for more information.

New Features

  1. REP-6969 Added support for more expressive filter determination in the <<architecture/system-model.adoc#,System Model>> using boolean operators.

Enhancements

  1. REP-7135 Improved the artifact deployment strategy to handle multiple Repose instances running concurrently.
  2. REP-7096 Updated the v9.0.0.0 ReposeRoutingServlet to be able to actually route requests.
    1. Note this servlet is not currently in use, but is included in the shipped artifacts.
  3. REP-7128 Updated the performance tests so that they have a more standard layout, and more fully allow integration in the IDE.

Bug Fixes

  1. NONE

Removed Features

  1. NONE

Known Issues

  1. REP-5531 While the Scripting filter schema indicates support for several languages, the Ruby and Lua implementations have multithreading issues and should not be used in this version of Repose.
  2. REP-6880 Repose will fail to load configuration files with embedded XSLT if the the XSLT Attribute Value Template (AVT, i.e., "{$param}") is used. The reason is that the Repose configuration output template tokens (i.e., "{$env_var$}") clash with the XSLT AVT tokens. The result is that the templating engine attempts to process the AVT (e.g., "{$param}") but cannot find the end of the "code island" (i.e., "$}") and so fails. This issue should only arise if the deprecated feature of embedding XSLT into a configuration file (such as the translation filter configuration) is used, and can be worked around by extracted the XSLT into a file referenced by the configuration file.

Deprecated Features

  1. NONE