commons-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Guillaume Déflache (JIRA) <>
Subject [jira] Commented: (JELLY-163) Allow Expressions to throw exceptions
Date Sun, 06 Sep 2009 05:19:57 GMT


Guillaume Déflache commented on JELLY-163:

AFAICS this was fixed (on trunk only ATM) as part of JELLY-286.
Also "Affects Version/s" field is wrong, since this also happens in 1.0 and anyway 1.1-beta-1
was never publicly released AFAIK.
And FWIW I fully agree with Paul, see
for details.

> Allow Expressions to throw exceptions
> -------------------------------------
>                 Key: JELLY-163
>                 URL:
>             Project: Commons Jelly
>          Issue Type: Improvement
>          Components: core / taglib.core
>    Affects Versions: 1.1-beta-1
>            Reporter: Hans Gilde
> Per a recent email from Paul Libbrecht, we should allow expressions to throw an exception.
Currently, the Expression interface doesn't throw exceptions.
> Issues:
> * currently, the script evaluation isn't terminated because of an expression exception.
should it be? by default, I mean. could this be another flag in the environment?
> * should the tag itself be given a way to intercept exceptions from Expressions? Expressions
are evaluated before the tag is run, so it normally wouldn't know anything about them.
> Email from Paul Libbrecht []:
> ~~~~~~~~~~~~~~~~~~~~~~~~
> Hi,
> One of the most frustrating place in jelly, to my taste, is when a jexl exception occurs...
Jelly complains (at least with good logging
> settings) but does not throw. Moreover, this complaint doesn't have a jelly line-number
which makes it somewhat hard.
> Is there really any wish that such an exception is not thrown ?
> thanks
> paul
> ~~~~~~~~~~~~~~~~~~~~~~~~~~~

This message is automatically generated by JIRA.
You can reply to this email to add a comment to the issue online.

View raw message