You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@commons.apache.org by "Henri Biestro (Jira)" <ji...@apache.org> on 2021/06/08 16:31:00 UTC

[jira] [Resolved] (JEXL-351) JXLT Template fails when using sandboxing

     [ https://issues.apache.org/jira/browse/JEXL-351?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Henri Biestro resolved JEXL-351.
--------------------------------
    Resolution: Fixed

Can not tag it properly (INFRA issue), should be Fixed in 3.2.1.

https://github.com/apache/commons-jexl/tree/04da59b8ca751196e7493d681d52ef21455f9780

> JXLT Template fails when using sandboxing
> -----------------------------------------
>
>                 Key: JEXL-351
>                 URL: https://issues.apache.org/jira/browse/JEXL-351
>             Project: Commons JEXL
>          Issue Type: Bug
>    Affects Versions: 3.2
>            Reporter: Henri Biestro
>            Assignee: Henri Biestro
>            Priority: Critical
>
> Regression, total loss of functionality.
> In 3.2:
> When the JEXL engine is built with a custom sandboxing Uberspect that strictly narrows the classes and methods allowed, the TemplateInterpreter methods may end up being in the blocked list. Since the interpreter relies on finding the methods to operate, the whole template silently fails with an empty content.
> The fix is to mimic 3.1, the AST nodes for the jexl:print and jexl:includes calls being interpreted directly.



--
This message was sent by Atlassian Jira
(v8.3.4#803005)