A new method getActionParameterTypes() has been added for the any type. It returns the required types as a sequence of strings, allowing reflection on action parameters, built-in methods, closures, and plug-in methods. See the API Reference for EPL (ApamaDoc) for more information.

For consistency with our recommended case for action methods, we have replaced the nextafter method on float and decimal with nextAfter. The previous method name will still work for compatibility, but we recommend you to begin using nextAfter instead.

The Management interface can now be used to fetch the list of configuration properties that the correlator was started with from EPL. This is available through the new getConfigProperties method on the com.apama.correlator.Component event. See also Using the Management interface and the API Reference for EPL (ApamaDoc) .

The Management interface now has another method for manipulating user-defined status values. Component.incrementUserStatus allows you to atomically increment or decrement a status value from multiple contexts. For more details, see the API Reference for EPL (ApamaDoc) .

When exceptions are thrown from EPL plug-ins that are written in Python or Java, the resulting stack trace when caught or logged in EPL now includes both the stack elements from within the plug-in as well as the ones within EPL. Thus, stack traces are no longer logged separately for exceptions from EPL plug-ins written in Java.