You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@tapestry.apache.org by "Jochen Kemnade (JIRA)" <ji...@apache.org> on 2014/05/21 11:06:38 UTC
[jira] [Closed] (TAP5-2059) Bridging to undefined clojure methods
may throw NullPointerException
[ https://issues.apache.org/jira/browse/TAP5-2059?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Jochen Kemnade closed TAP5-2059.
--------------------------------
Resolution: Not a Problem
No longer relevant to me
> Bridging to undefined clojure methods may throw NullPointerException
> --------------------------------------------------------------------
>
> Key: TAP5-2059
> URL: https://issues.apache.org/jira/browse/TAP5-2059
> Project: Tapestry 5
> Issue Type: Improvement
> Components: tapestry-clojure
> Affects Versions: 5.3.6, 5.4
> Reporter: Jochen Kemnade
> Priority: Minor
> Labels: NullPointerException, assertion, clojure, patch
> Attachments: 0001-Throw-an-exception-if-the-retrieved-Clojure-var-for-.patch
>
>
> When bridging to an undefined clojure method, the `Var` lookup will return `null`. When this `null` is injected into the `PlasticField`, either an `AssertionError` will be thrown, or, if assertions are disabled, a `NullPointerException` will eventually be thrown from somewhere deep in the generated bytecode. A meaningful exception would be better in that case.
--
This message was sent by Atlassian JIRA
(v6.2#6252)