InaccessibleObjectException when calling distinct on a stream in OGNL

[Luke-Sikina]

MyBatis version

3.5.9

Database vendor and version

MySQL 5.7

Test case or example project

Example project, linked to test case

Steps to reproduce

1. Checkout the project listed above
2. Make sure you are running Java 17+
3. Make sure you have docker installed (I used test containers to make the example cleaner)
4. In the project, run mvn clean install (If you don't use test containers a lot, this might take a minute to pull everything)

Expected result

Maven will compile the project, spin up the test db container, pass all tests, and build successfully.

Actual result

The build will fail because of a test failure. The test fails with the following error:

### Error querying database.  Cause: java.lang.reflect.InaccessibleObjectException: Unable to make public final java.util.stream.Stream java.util.stream.ReferencePipeline.distinct() accessible: module java.base does not "opens java.util.stream" to unnamed module @7f1dd5e7
### Cause: java.lang.reflect.InaccessibleObjectException: Unable to make public final java.util.stream.Stream java.util.stream.ReferencePipeline.distinct() accessible: module java.base does not "opens java.util.stream" to unnamed module @7f1dd5e7
        at com.sikina.mybatisproblem.ExampleMapperIntegrationTest.shouldGetThings(ExampleMapperIntegrationTest.java:43)

[harawata]

Hello @Luke-Sikina ,

Thank you for the report and the complete repro!

This problem has been fixed in 3.5.10 which is currently available in the snapshot repo.
We plan to release 3.5.10 soon, so it would be great if you could try the snapshot and see if there is any other issue.

Related issues:

• MyBatis needs to access java.lang and java.util . Not working anymore by default in Java 17 #2383
• WARNING: An illegal reflective access operation has occurred -> when using public method in non public class #2392
• Avoid illegal reflective access when possible orphan-oss/ognl#144

[Luke-Sikina]

@harawata Thank you for the quick response! I just tried using 3.5.10-SNAPSHOT and it worked perfectly. I even added some other logic that uses a more complex collector that I was concerned about, and it still worked perfectly. I've pushed the fixed unit test to a new branch in my repro repo, in case you need to refer to it: https://github.com/Luke-Sikina/mybatisproblem/tree/snapshot-fix

I'm not sure if you close issues when you cut the relevant release, or when you commit the fix, so I'm going to let you close this at your discretion.

Thank you for solving this; I'm looking forward to 3.5.10!

[harawata]

Thanks for the swift feedback!
And the update is reassuring. :D

Closing as a duplicate of #2392