[
https://issues.apache.org/jira/browse/TAP5-2330?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13993454#comment-13993454
]
Jochen Kemnade commented on TAP5-2330:
--------------------------------------
The problem is that the generated {{clientId}} is lost after the Zone's initial
rendering. During the update request, when {{zone.getClientId()}} is called
from {{AjaxResponseRendererImpl.addRender(ClientBodyElement)}}, the
{{clientId}} field is {{null}}.
I have a test for the issue but no (idea for a) fix yet.
> 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
> Priority: Critical
> 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)
