[Bug 57441] EL Lambda expression in a JSP fails with The function incr must be used with a prefix when a default namespace is not specified

2015-01-22 Thread bugzilla
https://issues.apache.org/bugzilla/show_bug.cgi?id=57441 Mark Thomas ma...@apache.org changed: What|Removed |Added Status|NEW |RESOLVED

[Bug 57441] EL Lambda expression in a JSP fails with The function incr must be used with a prefix when a default namespace is not specified

2015-01-20 Thread bugzilla
https://issues.apache.org/bugzilla/show_bug.cgi?id=57441 --- Comment #4 from Mark Thomas ma...@apache.org --- (In reply to Konstantin Kolinko from comment #3) Is it at all possible to reliably validate functions at compile time? You are right. As of EL 3.0 this is no longer possible. Maybe

[Bug 57441] EL Lambda expression in a JSP fails with The function incr must be used with a prefix when a default namespace is not specified

2015-01-19 Thread bugzilla
https://issues.apache.org/bugzilla/show_bug.cgi?id=57441 --- Comment #3 from Konstantin Kolinko knst.koli...@gmail.com --- Is it at all possible to reliably validate functions at compile time? Maybe whitelist functions that have name only with no prefix? BTW, it is possible to use

[Bug 57441] EL Lambda expression in a JSP fails with The function incr must be used with a prefix when a default namespace is not specified

2015-01-17 Thread bugzilla
https://issues.apache.org/bugzilla/show_bug.cgi?id=57441 --- Comment #2 from Mark Thomas ma...@apache.org --- I think it is time to ditch Jasper's partial EL parser and use o.a.el.lang.ExpressionBuilder.createNode() to fully parse the EL with a 'proper' EL implementation and then process those

[Bug 57441] EL Lambda expression in a JSP fails with The function incr must be used with a prefix when a default namespace is not specified

2015-01-13 Thread bugzilla
https://issues.apache.org/bugzilla/show_bug.cgi?id=57441 Konstantin Kolinko knst.koli...@gmail.com changed: What|Removed |Added OS||All