Flex Gateway新着情報
Governance新着情報
Monitoring API ManagerSupport Category: Select
Use the Java module to invoke Java code.
March 25, 2024
Application/Service | Version |
---|---|
Mule |
4.1.1 and later |
OpenJDK |
8, 11, and 17 |
Issue Resolution | ID |
---|---|
The spring-core library is upgraded to version 5.3.33 to address reported security vulnerabilities. |
W-15194448 |
December 12, 2023
This connector is now compatible with Java 17.
Application/Service | Version |
---|---|
Mule |
4.1.1 and later |
OpenJDK |
8, 11, and 17 |
June 21, 2023
Application/Service | Version |
---|---|
Mule |
4.1.1 and later |
Issue Resolution | ID |
---|---|
The spring-core library is upgraded to version 5.3.28 to address reported security vulnerabilities. |
W-13622235 |
June 28, 2022
Upgraded versions of dependencies.
Application/Service |
Version |
Mule |
4.1.1 and later |
August 17, 2021
Optimized the connector to improve its overall stability and performance. (JM-35)
Application/Service |
Version |
Mule |
4.1.1 and later |
April 8, 2021
Removed dependencies included in the Mule runtime engine to avoid warning messages during startup (JM-34)
December 9, 2019
Wrong OutputType for a method that returns a java.lang.Object type. (JM-14)
MUnit tests for metadata validation. (MU-1529)
Upgrade mule-extensions-parent, mule-core-modules-parent and mule-ee-core-modules-parent to 1.1.6. (MULE-17121)
Upgrade MUnit version to 2.2.1. (MULE-17301)
August 14, 2019
Change execution pool to CPU_LITE for new instance operations. (MULE-17326)
Change execution pool to IO for invoke operations. (MULE-17329)
May 30, 2019
Java module fails to invoke method that receives Optional<Pojo> (MULE-16932)
May 29, 2019
Java module fails to transform null into an empty Optional. (MULE-16918)
January 14, 2019
Fixed an issue with invoking a method from a class that implements an interface with generics. This would produce a warning that there were multiple methods found that match the provided method.
JavaModule: no longer throws WARN messages with Generic interface implementation. (MULE-16316)
September 6, 2018
It’s now possible to configure the Output MimeType of the Invoke and Invoke Static Operations.
Improved error handling, the connector used to not show the real error that occurred when executing Java methods.
New functions getRootCause
and isCausedBy
are now available to introspect Throwables.
In the extreme case where two parameters have the same simple name, such as
some.Pojo
and other.Pojo
the full qualifier name can be used to avoid issues.
JavaModule: Support output MimeType parameter for runtime inference. (MULE-15283)
Java Module: Improve Error cause propagation. (MULE-15540)
Java Module: does not propagate execution error. (MULE-15262)
Java Module invokeStatic declares an error that is never thrown. (MULE-15461)
JavaModule: Support full qualifier name for parameter types to identify methods. (MULE-15009)
Migrate JavaModule tests to MTF. (MULE-15076)
Java Module: improve method not found error message. (MULE-15263)
Java Module: 'new' operation does not declare INVOCATION error. (MULE-15538)
Java Module: Fail to extract exception cause with default value. (MULE-15597)
August 14, 2019
Provide proper classloading error information. (MULE-14938)
Improve error messages and exception propagation. (MULE-15263)
Change execution pool to CPU_LITE for new instance operations. (MULE-17326)
Change execution pool to IO for invoke operations. (MULE-17329)
InvokeStatic declares an error that is never thrown. (MULE-15461)
May 11, 2018
Fixed an issue that made it impossible to pass null as a parameter.
Now when the arguments are passed by with their canonical name (arg0, arg1, etc.), parameter matching will be done by position.
JavaModule: Do best effort to do invocation with arg0, arg1… (MULE-15008)
null values causes Exception in parameterNeedsTransformation. (MULE-14990)
May 7, 2018
When argument types don’t match the java function arguments, a best effort will be done to transform these arguments.
Java module doesn’t transform the arguments. (MULE-14861)
March 23, 2018
Fixed an issue that happened when calling static methods from different classes with the same signature.
Invoke static second call wrong. (MULE-14785)