Skip to content

Conversation

@harawata
Copy link
Member

  • Refactoring: moving OGNL related code to OgnlExpressionParser
  • Support type alias in OGNL expression

This is a revised version of #1594 and should fix #416 .
The core part is written by @kazuki43zoo .

There was a thread in discussion ( #3597 ), but I might have deleted it accidentally...
If the author of #3597 sees this, please leave a comment.

The purpose is to avoid OGNL specific classes from being referenced in various places.
We do not have any reason to replace OGNL with something else at the moment, but if/when it becomes necessary, this change will make the transition easier.
Instead of writing fully-qualified name, it is now possible to use alias in `@...@` for example.

I found two corner cases (see the tests with `@Disabled`), but they won't be a big problem, I think.
@harawata harawata requested a review from kazuki43zoo January 30, 2026 19:20
@coveralls
Copy link

Coverage Status

coverage: 87.368% (-0.06%) from 87.429%
when pulling 0e9f683 on harawata:type-alias-support-in-ognl
into 7000674 on mybatis:master.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

Please support typeAliases of configuration on OgnlClassResolver

2 participants