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/31 11:38:01 UTC

[jira] [Reopened] (TAP5-2330) NullPointerException when updating a Zone with no clientId

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

Jochen Kemnade reopened TAP5-2330:
----------------------------------


The changes to JSONObject will make things harder to debug, this way, the error will probably end up to in the client, trying to find a zone for {{null}}.
I think we shouldn't allow {{null}} to be added to a JSONArray in the first place instead of pretending it was {{JSONObject.NULL}} later.

> NullPointerException when updating a Zone with no clientId
> ----------------------------------------------------------
>
>                 Key: TAP5-2330
>                 URL: https://issues.apache.org/jira/browse/TAP5-2330
>             Project: Tapestry 5
>          Issue Type: Bug
>          Components: tapestry-core, tapestry-json
>    Affects Versions: 5.4
>            Reporter: Jochen Kemnade
>            Assignee: Thiago H. de Paula Figueiredo
>            Priority: Critical
>              Labels: month-of-tapestry
>             Fix For: 5.4
>
>         Attachments: 0001-add-test-for-TAP5-2330.patch
>
>
> If a Zone update is performed via AjaxResponseRenderer and the Zone has no id parameter, the RenderCommand creates a JSONArray with null as its first element. If assertions are disabled for the JVM, this leads to a NullPointerException in JSONObject.printValue(JSONPrintSession, Object).



--
This message was sent by Atlassian JIRA
(v6.2#6252)