@mybatis/committers WDYT this PR?

Thank you, @kazuki43zoo !

This adds extra text processing to every expression on top of OGNL.
It looks a little bit too expensive just to save some typing.

@harawata

Thanks for your comment!!

This adds extra text processing to every expression on top of OGNL.

Probably this changes will be affect only expression that access class(e.g. expression with start with @ or new operation). In other words, I think many expressions using with the MyBatis does not affect. Is my opinion wrong?

@kazuki43zoo ,

I'm sorry about the lack of response.
I didn't forget, but wanted to take a deeper look.

First of all, you are right about the side effect.
I'm sorry about the poor review. :D

Regarding the implementation, passing OgnlClassResolver to various constructor does not look great.

I think, we should drop ExpressionEvaluator and move its functionality (getValue, evaluateBoolean, evaluateIterable) to DynamicContext.
Then, various SqlNode implementations can call those methods from its apply().
In DynamicContext, TypeAliasRegistry can be retrieved from Configuration, of course.

By the way, I don't think we need the fallback for java.lang classes as useful classes are already registered in MyBatis' TypeAliasRegistry.

If my explanation does not make sense, give me some time and I'll try the idea myself (it's possible that I am missing something).