New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Return meaningful values for MessageTask getMethodName function[API-2037] #25020
Return meaningful values for MessageTask getMethodName function[API-2037] #25020
Conversation
The following is the list of message tasks which will continue returning null after this PR is merged.
|
The job Click to expand the log file-------------------------- -------TEST FAILURE------- -------------------------- [INFO] Results: [INFO] [ERROR] Failures: [ERROR] StreamKafkaPTest.when_processingGuaranteeNoneWithConsumerGroup_then_continueFromLastReadMessageAfterJobRestart:267->testWithJobRestart:350->HazelcastTestSupport.assertTrueEventually:1184->HazelcastTestSupport.assertTrueEventually:1165->lambda$testWithJobRestart$4:350 expected:<200> but was:<193> [INFO] [ERROR] Tests run: 51, Failures: 1, Errors: 0, Skipped: 1 [INFO] |
...rc/main/java/com/hazelcast/client/impl/protocol/task/cache/CacheCreateConfigMessageTask.java
Outdated
Show resolved
Hide resolved
...java/com/hazelcast/client/impl/protocol/task/cache/CacheListenerRegistrationMessageTask.java
Outdated
Show resolved
Hide resolved
...ast/client/impl/protocol/task/executorservice/ExecutorServiceSubmitToAddressMessageTask.java
Outdated
Show resolved
Hide resolved
...t/client/impl/protocol/task/executorservice/ExecutorServiceSubmitToPartitionMessageTask.java
Outdated
Show resolved
Hide resolved
...st/src/main/java/com/hazelcast/client/impl/protocol/task/map/MapDestroyCacheMessageTask.java
Outdated
Show resolved
Hide resolved
...n/java/com/hazelcast/client/impl/protocol/task/transaction/TransactionCommitMessageTask.java
Outdated
Show resolved
Hide resolved
...n/java/com/hazelcast/client/impl/protocol/task/transaction/TransactionCreateMessageTask.java
Outdated
Show resolved
Hide resolved
...java/com/hazelcast/client/impl/protocol/task/transaction/TransactionRollbackMessageTask.java
Outdated
Show resolved
Hide resolved
...java/com/hazelcast/client/impl/protocol/task/transaction/XATransactionCommitMessageTask.java
Outdated
Show resolved
Hide resolved
...va/com/hazelcast/client/impl/protocol/task/transaction/XATransactionRollbackMessageTask.java
Outdated
Show resolved
Hide resolved
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
lgtm except I think we should make sure we document these if the user will need to use these strings. According to https://docs.hazelcast.com/imdg/4.2/security/security-interceptor#latest-banner, the user needs to know the exact method name.
If they need to know the exact strings, we should list these strings in our documentation, together with the methods each string corresponds to. e.g "destroyCache" -> "QueryCache.destroy" and "IMap.destroy"
Another question: Can we use the same strings (e.g using "create" for two different message tasks) in two different getMethodName's? What happens in that case ? If it is not allowed, do we validate if we are not duplicating any string in getMethodName?
@srknzl The unique one is service name + method name, hence, it is ok to have the same method name e.g. using "create" for two different message tasks since their service names will differ. |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Could you place the names in a separate constant class to make it a public API?
I think we need to cover more classes - the comment mentions CreateProxyMessageTask
and DestroyProxyMessageTask
.
Also these ones from your list caught my eye:
DeployClassesMessageTask.java (1 usage found)
CacheDestroyMessageTask.java (1 usage found)
We could also consider the ones with *Config*
in the name.
I will put them in a new constants file @kwart What about the Can the user do security check on proxy creation which happens for each data structure? |
@kwart @srknzl What about using enums instead of free String in the parameter.
Is there any specific reason to make the parameter as free String? |
As discussed internally, the enums (compared to free Strings) can lead to
|
The job Click to expand the log file---------ERRORS----------- -------------------------- [ERROR] /home/jenkins/jenkins_slave/workspace/Hazelcast-pr-builder/hazelcast/src/main/java/com/hazelcast/security/SecurityInterceptorConstants.java:19:1: Utility classes should not have a public or default constructor. [HideUtilityClassConstructor] -------------------------- [ERROR] Failed to execute goal org.apache.maven.plugins:maven-checkstyle-plugin:3.3.0:checkstyle (default) on project hazelcast: An error has occurred in Checkstyle report generation. Failed during checkstyle execution: There is 1 error reported by Checkstyle 8.38 with /home/jenkins/jenkins_slave/workspace/Hazelcast-pr-builder/checkstyle/checkstyle.xml ruleset. -> [Help 1] -------------------------- [ERROR] -------------------------- [ERROR] Re-run Maven using the -X switch to enable full debug logging. -------------------------- [ERROR] -------------------------- [ERROR] For more information about the errors and possible solutions, please read the following articles: -------------------------- [ERROR] [Help 1] http://cwiki.apache.org/confluence/display/MAVEN/MojoExecutionException -------------------------- [ERROR] -------------------------- [ERROR] After correcting the problems, you can resume the build with the command -------------------------- [ERROR] mvn -rf :hazelcast -------------------------- |
The job Click to expand the log file---------ERRORS----------- -------------------------- [ERROR] /appdisk/jenkins/jenkins_slave/workspace/Hazelcast-pr-compiler/hazelcast/src/main/java/com/hazelcast/security/SecurityInterceptorConstants.java:19:1: Utility classes should not have a public or default constructor. [HideUtilityClassConstructor] -------------------------- [ERROR] Failed to execute goal org.apache.maven.plugins:maven-checkstyle-plugin:3.3.0:checkstyle (default) on project hazelcast: An error has occurred in Checkstyle report generation. Failed during checkstyle execution: There is 1 error reported by Checkstyle 8.38 with /appdisk/jenkins/jenkins_slave/workspace/Hazelcast-pr-compiler/checkstyle/checkstyle.xml ruleset. -> [Help 1] -------------------------- [ERROR] -------------------------- [ERROR] Re-run Maven using the -X switch to enable full debug logging. -------------------------- [ERROR] -------------------------- [ERROR] For more information about the errors and possible solutions, please read the following articles: -------------------------- [ERROR] [Help 1] http://cwiki.apache.org/confluence/display/MAVEN/MojoExecutionException -------------------------- [ERROR] -------------------------- [ERROR] After correcting the problems, you can resume the build with the command -------------------------- [ERROR] mvn -rf :hazelcast -------------------------- |
@@ -75,7 +76,7 @@ public Permission getRequiredPermission() { | |||
|
|||
@Override | |||
public String getMethodName() { | |||
return "removeCachePartitionLostListener"; | |||
return SecurityInterceptorConstants.REMOVE_PARTITION_LOST_LISTENER; |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
The string is changed as I see: removePartitionLostListener. Is it intentional ?
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Yes, it is intentional. There is the getServiceName
method as well at the Security interceptor which identifies if it is cache service or not, hence no need for the work Cache
in the method name and I removed it.
@@ -77,6 +78,6 @@ public Object[] getParameters() { | |||
|
|||
@Override | |||
public String getMethodName() { | |||
return "iterator"; | |||
return SecurityInterceptorConstants.FETCH; |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Should not this be SecurityInterceptorConstants.ITERATE? 🤔
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
They actually correspond to the hasNext and next methods of the iterator. I am changing it back to iterator as suggested. fix commit
The job Click to expand the log file---------ERRORS----------- -------------------------- [ERROR] /home/jenkins/jenkins_slave/workspace/Hazelcast-pr-builder/hazelcast/src/main/java/com/hazelcast/security/SecurityInterceptorConstants.java:24:1: Utility classes should not have a public or default constructor. [HideUtilityClassConstructor] -------------------------- [ERROR] Failed to execute goal org.apache.maven.plugins:maven-checkstyle-plugin:3.3.0:checkstyle (default) on project hazelcast: An error has occurred in Checkstyle report generation. Failed during checkstyle execution: There is 1 error reported by Checkstyle 8.38 with /home/jenkins/jenkins_slave/workspace/Hazelcast-pr-builder/checkstyle/checkstyle.xml ruleset. -> [Help 1] -------------------------- [ERROR] -------------------------- [ERROR] Re-run Maven using the -X switch to enable full debug logging. -------------------------- [ERROR] -------------------------- [ERROR] For more information about the errors and possible solutions, please read the following articles: -------------------------- [ERROR] [Help 1] http://cwiki.apache.org/confluence/display/MAVEN/MojoExecutionException -------------------------- [ERROR] -------------------------- [ERROR] After correcting the problems, you can resume the build with the command -------------------------- [ERROR] mvn -rf :hazelcast -------------------------- |
The job Click to expand the log file-------------------------- ---------SUMMARY---------- -------------------------- [ERROR] COMPILATION ERROR : -------------------------- [ERROR] /appdisk/jenkins/jenkins_slave/workspace/Hazelcast-pr-EE-compiler/hazelcast/hazelcast/src/main/java/com/hazelcast/client/impl/protocol/task/map/MapAddEntryListenerMessageTask.java:[30,8] com.hazelcast.client.impl.protocol.task.map.MapAddEntryListenerMessageTask is not abstract and does not override abstract method getMethodName() in com.hazelcast.client.impl.protocol.task.AbstractMessageTask -------------------------- ---------ERRORS----------- -------------------------- [ERROR] COMPILATION ERROR : -------------------------- [ERROR] /appdisk/jenkins/jenkins_slave/workspace/Hazelcast-pr-EE-compiler/hazelcast/hazelcast/src/main/java/com/hazelcast/client/impl/protocol/task/map/MapAddEntryListenerMessageTask.java:[30,8] com.hazelcast.client.impl.protocol.task.map.MapAddEntryListenerMessageTask is not abstract and does not override abstract method getMethodName() in com.hazelcast.client.impl.protocol.task.AbstractMessageTask -------------------------- [ERROR] Failed to execute goal org.apache.maven.plugins:maven-compiler-plugin:3.11.0:compile (default-compile) on project hazelcast: Compilation failure -------------------------- [ERROR] /appdisk/jenkins/jenkins_slave/workspace/Hazelcast-pr-EE-compiler/hazelcast/hazelcast/src/main/java/com/hazelcast/client/impl/protocol/task/map/MapAddEntryListenerMessageTask.java:[30,8] com.hazelcast.client.impl.protocol.task.map.MapAddEntryListenerMessageTask is not abstract and does not override abstract method getMethodName() in com.hazelcast.client.impl.protocol.task.AbstractMessageTask -------------------------- [ERROR] -> [Help 1] -------------------------- [ERROR] -------------------------- [ERROR] To see the full stack trace of the errors, re-run Maven with the -e switch. -------------------------- [ERROR] Re-run Maven using the -X switch to enable full debug logging. -------------------------- [ERROR] -------------------------- [ERROR] For more information about the errors and possible solutions, please read the following articles: -------------------------- [ERROR] [Help 1] http://cwiki.apache.org/confluence/display/MAVEN/MojoFailureException -------------------------- [ERROR] -------------------------- [ERROR] After correcting the problems, you can resume the build with the command -------------------------- [ERROR] mvn -rf :hazelcast -------------------------- |
The job Click to expand the log file---------ERRORS----------- -------------------------- [ERROR] /home/jenkins/jenkins_slave/workspace/Hazelcast-pr-compiler/hazelcast/src/main/java/com/hazelcast/security/SecurityInterceptorConstants.java:24:1: Utility classes should not have a public or default constructor. [HideUtilityClassConstructor] -------------------------- [ERROR] Failed to execute goal org.apache.maven.plugins:maven-checkstyle-plugin:3.3.0:checkstyle (default) on project hazelcast: An error has occurred in Checkstyle report generation. Failed during checkstyle execution: There is 1 error reported by Checkstyle 8.38 with /home/jenkins/jenkins_slave/workspace/Hazelcast-pr-compiler/checkstyle/checkstyle.xml ruleset. -> [Help 1] -------------------------- [ERROR] -------------------------- [ERROR] Re-run Maven using the -X switch to enable full debug logging. -------------------------- [ERROR] -------------------------- [ERROR] For more information about the errors and possible solutions, please read the following articles: -------------------------- [ERROR] [Help 1] http://cwiki.apache.org/confluence/display/MAVEN/MojoExecutionException -------------------------- [ERROR] -------------------------- [ERROR] After correcting the problems, you can resume the build with the command -------------------------- [ERROR] mvn -rf :hazelcast -------------------------- |
fb29146
to
28cb19f
Compare
I am not putting any security checks on the compact schema management tasks at |
@@ -96,7 +97,7 @@ public String getDistributedObjectName() { | |||
|
|||
@Override | |||
public String getMethodName() { | |||
return null; | |||
return SecurityInterceptorConstants.RECOVER; |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
collect transactions and recover? What is the relation ?
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
When I trace this task and try to find the associated user API, I found that the user API is XAResource.recover
API and hence I named it it this way to relate to the user API.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
approving with one comment above
run-ee-tests |
run-ee-nightly-tests |
The job Click to expand the log file---------ERRORS----------- -------------------------- [ERROR] Tests run: 13, Failures: 1, Errors: 0, Skipped: 0, Time elapsed: 20.14 s <<< FAILURE! -- in com.hazelcast.client.security.SetSecurityInterceptorTest -------------------------- [ERROR] com.hazelcast.client.security.SetSecurityInterceptorTest.iterator -- Time elapsed: 20.13 s <<< FAILURE! -------------------------- [ERROR] Tests run: 29, Failures: 1, Errors: 0, Skipped: 10, Time elapsed: 20.22 s <<< FAILURE! -- in com.hazelcast.client.security.CacheSecurityInterceptorTest -------------------------- [ERROR] com.hazelcast.client.security.CacheSecurityInterceptorTest.removeAll -- Time elapsed: 20.20 s <<< FAILURE! -------------------------- [ERROR] Tests run: 5, Failures: 0, Errors: 2, Skipped: 0, Time elapsed: 843.0 s <<< FAILURE! -- in com.hazelcast.internal.tstore.compaction.PartitionCompactorTest -------------------------- [ERROR] com.hazelcast.internal.tstore.compaction.PartitionCompactorTest.test_partition_compactor_with_index_on_owner_and_backup -- Time elapsed: 302.3 s <<< ERROR! -------------------------- [ERROR] com.hazelcast.internal.tstore.compaction.PartitionCompactorTest.test_partition_compactor_with_null_index_on_owner_and_backup -- Time elapsed: 300.8 s <<< ERROR! -------------------------- [ERROR] Failures: -------------------------- [ERROR] CacheSecurityInterceptorTest.removeAll Expected: removeAll, Actual: removeAllKeys -------------------------- [ERROR] SetSecurityInterceptorTest.iterator Expected: iterator, Actual: getAll -------------------------- [ERROR] Errors: -------------------------- [ERROR] PartitionCompactorTest.test_partition_compactor_with_index_on_owner_and_backup:149 ? TestTimedOut test timed out after 300000 milliseconds -------------------------- [ERROR] PartitionCompactorTest.test_partition_compactor_with_null_index_on_owner_and_backup:205 ? TestTimedOut test timed out after 300000 milliseconds -------------------------- [ERROR] Tests run: 10183, Failures: 2, Errors: 2, Skipped: 78 -------------------------- [ERROR] There are test failures. -------------------------- -------------------------- -------TEST FAILURE------- -------------------------- [INFO] Results: [INFO] [ERROR] Failures: [ERROR] CacheSecurityInterceptorTest.removeAll Expected: removeAll, Actual: removeAllKeys [ERROR] SetSecurityInterceptorTest.iterator Expected: iterator, Actual: getAll [ERROR] Errors: [ERROR] PartitionCompactorTest.test_partition_compactor_with_index_on_owner_and_backup:149 ? TestTimedOut test timed out after 300000 milliseconds [ERROR] PartitionCompactorTest.test_partition_compactor_with_null_index_on_owner_and_backup:205 ? TestTimedOut test timed out after 300000 milliseconds [INFO] [ERROR] Tests run: 10183, Failures: 2, Errors: 2, Skipped: 78 [INFO] |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Could you also send a fix for the 2 EE tests that fail with the new names?
If we proceed with the rename (i.e. change from a not-null value to another one), then these instances should be listed in the Release Notes as breaking changes. We should make doc and support teams aware of it.
Overall, I like the changes. The majority of my comments are just process ones :)
@@ -70,14 +75,24 @@ public String getDistributedObjectName() { | |||
|
|||
@Override | |||
public Object[] getParameters() { | |||
Map<Data, Data> map = createMap(); |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Does it make sense to put the parameters on a new map? The current implementation will create the Map
every time once the security is enabled - even if there is no SecurityInterceptor
configured.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
This is to make the interceptor test at here work properly and it makes sense since the parameter of the ICache.putAll
method receives a map. Yes, it is one more map creation but it makes the API more user friendly. Let me know if it is OK or I am happy to revert it if we agree on returning the parameters.entries
public java.util.List<java.util.Map.Entry<com.hazelcast.internal.serialization.Data, com.hazelcast.internal.serialization.Data>> entries;
hazelcast/src/main/java/com/hazelcast/security/SecurityInterceptorConstants.java
Show resolved
Hide resolved
@@ -77,7 +78,7 @@ public String getDistributedObjectName() { | |||
|
|||
@Override | |||
public String getMethodName() { | |||
return "iterator"; | |||
return SecurityInterceptorConstants.ITERATOR_FETCH_KEYS; |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
This should go to the Release Notes.
@@ -105,7 +106,7 @@ public String getDistributedObjectName() { | |||
|
|||
@Override | |||
public String getMethodName() { | |||
return "iterator"; | |||
return SecurityInterceptorConstants.ITERATOR_FETCH_WITH_QUERY; |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
RN
@@ -67,7 +68,7 @@ public String getDistributedObjectName() { | |||
|
|||
@Override | |||
public String getMethodName() { | |||
return "projectWithPredicate"; | |||
return SecurityInterceptorConstants.PROJECT; |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
RN
@@ -76,7 +77,7 @@ public String getDistributedObjectName() { | |||
|
|||
@Override | |||
public String getMethodName() { | |||
return "getResultTimeout"; | |||
return SecurityInterceptorConstants.GET_RESULT; |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
RN
@@ -82,7 +83,7 @@ public String getDistributedObjectName() { | |||
|
|||
@Override | |||
public String getMethodName() { | |||
return "getResultTimeout"; | |||
return SecurityInterceptorConstants.GET_RESULT; |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
RN
@@ -72,7 +73,7 @@ public Permission getRequiredPermission() { | |||
|
|||
@Override | |||
public String getMethodName() { | |||
return "iterator"; | |||
return SecurityInterceptorConstants.GET_ALL; |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
RN
@@ -75,7 +76,7 @@ public String getDistributedObjectName() { | |||
|
|||
@Override | |||
public String getMethodName() { | |||
return "set"; | |||
return SecurityInterceptorConstants.ADD; |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
RN
@@ -75,7 +76,7 @@ public String getDistributedObjectName() { | |||
|
|||
@Override | |||
public String getMethodName() { | |||
return "removeEntry"; | |||
return SecurityInterceptorConstants.REMOVE; |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
RN
…d non-null method names to some of the message tasks which were missing the names and can be used in security interceptor since they are related to the user method calls. The ones which return null for the getMethodName function are the internally used or not directly related to the user API calls. Also, removed the default null returning implementations in some of the base message tasks.
…terceptor is being called. Removed the name from the CacheCreateConfigMessageTask since no such interception is provided for all other structures. Fixed the returned parameters in loadAll, and putAll message tasks and opened the previously ignored tests.
…stants class `SecurityInterceptorConstants`.
d743c62
to
0c8def3
Compare
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Thanks for the enhancements, Ihsan. 👍
The job Click to expand the log file---------ERRORS----------- -------------------------- [ERROR] Tests run: 13, Failures: 0, Errors: 1, Skipped: 0, Time elapsed: 3.172 s <<< FAILURE! -- in com.hazelcast.internal.tpcengine.nio.NioAsyncServerSocketTest -------------------------- [ERROR] com.hazelcast.internal.tpcengine.nio.NioAsyncServerSocketTest.test_createCloseLoop_withSameReactor -- Time elapsed: 0.126 s <<< ERROR! -------------------------- [ERROR] Errors: -------------------------- [ERROR] NioAsyncServerSocketTest>AsyncServerSocketTest.test_createCloseLoop_withSameReactor:255 ? UncheckedIO Failed to bind to /127.0.0.1:5001 -------------------------- [ERROR] Tests run: 292, Failures: 0, Errors: 1, Skipped: 0 -------------------------- [ERROR] -------------------------- |
run-lab-run |
…me (#25551) Fixed the incorrectly changed method names at [merged PR](#25020) back to the original name. Fixes the test failure at [this](hazelcast/hazelcast-enterprise#6548) PR [run](https://jenkins.hazelcast.com/job/Hazelcast-EE-pr-builder/9256/#showFailuresLink).
…037] (hazelcast#25020) Return meaningful values for MessageTask `getMethodName` function. Added non-null method names to some of the message tasks which were missing the names and can be used in security interceptor since they are related to the user method calls. The ones which return null for the `getMethodName` function are the internally used or not directly related to the user API calls. Also, removed the default null returning implementations in some of the base message tasks. The changes at the method names should be mentioned at the Release Notes. !!! EE PR: hazelcast/hazelcast-enterprise#6252
…me (hazelcast#25551) Fixed the incorrectly changed method names at [merged PR](hazelcast#25020) back to the original name. Fixes the test failure at [this](hazelcast/hazelcast-enterprise#6548) PR [run](https://jenkins.hazelcast.com/job/Hazelcast-EE-pr-builder/9256/#showFailuresLink).
…037] (hazelcast#25020) Return meaningful values for MessageTask `getMethodName` function. Added non-null method names to some of the message tasks which were missing the names and can be used in security interceptor since they are related to the user method calls. The ones which return null for the `getMethodName` function are the internally used or not directly related to the user API calls. Also, removed the default null returning implementations in some of the base message tasks. The changes at the method names should be mentioned at the Release Notes. !!! EE PR: hazelcast/hazelcast-enterprise#6252
…037] (hazelcast#25020) Return meaningful values for MessageTask `getMethodName` function. Added non-null method names to some of the message tasks which were missing the names and can be used in security interceptor since they are related to the user method calls. The ones which return null for the `getMethodName` function are the internally used or not directly related to the user API calls. Also, removed the default null returning implementations in some of the base message tasks. The changes at the method names should be mentioned at the Release Notes. !!! EE PR: hazelcast/hazelcast-enterprise#6252
…037] (hazelcast#25020) Return meaningful values for MessageTask `getMethodName` function. Added non-null method names to some of the message tasks which were missing the names and can be used in security interceptor since they are related to the user method calls. The ones which return null for the `getMethodName` function are the internally used or not directly related to the user API calls. Also, removed the default null returning implementations in some of the base message tasks. The changes at the method names should be mentioned at the Release Notes. !!! EE PR: hazelcast/hazelcast-enterprise#6252
Return meaningful values for MessageTask
getMethodName
function. Added non-null method names to some of the message tasks which were missing the names and can be used in security interceptor since they are related to the user method calls.The ones which return null for the
getMethodName
function are the internally used or not directly related to the user API calls.Also, removed the default null returning implementations in some of the base message tasks.
EE PR: https://github.com/hazelcast/hazelcast-enterprise/pull/6252