OGNLContext deprecated constructor crashes about ognl HOT 9 CLOSED

Are you sure it's about the line 170?

from ognl.

Sorry, I messed it up. It is line 140 with a RuntimeException. In line 120 the extensive constructor is invoked with null reference for parameter memberAccess. In line 137 is a null reference check on memberAccess which in turn always must lead to the RuntimeException.

from ognl.

The best option I see is to drop that constructor..

from ognl.

If no meaningful or 'cheap' default implementation for MemberAccess can be provided I tend to agree.

from ognl.

Yeah... that's why I have removed the default implementation from the main code and moved it into tests - it was quite often used to replace a framework's specific implementation by hackers. And that's why OGNL 3.2.x requires to provide your own implementation, even as a copy of the default one based on the one used in tests.

from ognl.

Also please be aware that 3.2.x line is still a work-in-progress - maybe I should express that better

from ognl.

Hi.

Dropping the single-argument constructor: https://github.com/jkuhnert/ognl/blob/6de4049f093eb643332bbf14090006fac516393c/src/main/java/ognl/OgnlContext.java#L121 that will now always fail with an exception seems reasonable to me.

At the same time, would it be beneficial to replace the generic RuntimeException exception: https://github.com/jkuhnert/ognl/blob/6de4049f093eb643332bbf14090006fac516393c/src/main/java/ognl/OgnlContext.java#L144
with a more specific IllegalArgumentException instead ?

The updated exception could be something like:

throw new IllegalArgumentException("MemberAccess implementation must be provided - null not permitted!");

from ognl.

Good idea, if no objections let's do it :)

from ognl.

OGNL 3.2.14 is out

from ognl.