-
Notifications
You must be signed in to change notification settings - Fork 12.9k
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
WARNING: An illegal reflective access operation has occurred -> when using public method in non public class #2392
Comments
The problem also occurs on 3.5.7. I also run with
|
Hello @filiphr , Please use
Duplicate of #2383 |
Thanks for the hint @harawata. I changed to However, I still think that the issue will happen for non collections in a similar situation, a public method on a non public class |
Glad to know it worked! Test expressions are evaluated by OGNL, so if you think there is a room for improvement, submit the enhancement request to their tracker : https://github.com/jkuhnert/ognl/issues |
This should be fixed by #2423 The OGNL issue is orphan-oss/ognl#144 (big thanks to @Farbfetzen !) You can verify the fix with 3.5.10-SNAPSHOT . Thank you for the report! |
That is great to hear @harawata. Thanks for letting me know |
MyBatis version
3.5.6
Database vendor and version
Not important
Steps to reproduce
Collections.emptyList()
test
expression in XML e.g.parameter.isEmpty()
Expected result
No illegal reflective access warning
Actual result
WARNING: An illegal reflective access operation has occurred
WARNING: Illegal reflective access by org.apache.ibatis.ognl.AccessibleObjectHandlerPreJDK9 (file:/~/.m2/repository/org/mybatis/mybatis/3.5.6/mybatis-3.5.6.jar) to method java.util.Collections$EmptyList.isEmpty()
WARNING: Please consider reporting this to the maintainers of org.apache.ibatis.ognl.AccessibleObjectHandlerPreJDK9
WARNING: Use --illegal-access=warn to enable warnings of further illegal reflective access operations
WARNING: All illegal access operations will be denied in a future release
The text was updated successfully, but these errors were encountered: