Constructor of OgnlContext with single Map Parameter throws Runtime Exception about ognl HOT 7 CLOSED

Nope but see FAQ

from ognl.

Hello, Sorry for my last question which was a bit overhasty. I found this info in the FAQ now. However, could it make sense to use it part of the single arg constructor? Currently, the constructor is not usable - and the Default class is part of sc/test so i need to copy it manually. Developers migrating from version 3.2 will get runtime exceptions.
Greetings

from ognl.

What's wrong in providing your own default implementation? Most of the security breaches were because a hacker was able to use the provided default implementation. Also providing your own implementation increases security awareness and allows users control how the security is applied.

from ognl.

Providing a custom Implementation is a good issue. In my case, i used a 3rd Party Library (thymeleaf) invoking the single arg constructor causing an exception. As it is now marked as deprecated will help here, so that libraries taking care of that issue. Thanks

from ognl.

using SpringTemplateEngine replace TemplateEngine,will fixed it

from ognl.

Providing a custom Implementation is a good issue. In my case, i used a 3rd Party Library (thymeleaf) invoking the single arg constructor causing an exception. As it is now marked as deprecated will help here, so that libraries taking care of that issue. Thanks

Hi, @escv . We have stuck in the exact same problem with thymeleaf (seems to be dead for years).

haven't you by chance solved the problem?

from ognl.

Maybe just in case of backward compatibility it would be good to introduce a in-fly creating implementation, still have the constructor marked as deprecated but useable.

from ognl.