[
https://issues.apache.org/jira/browse/TAP5-931?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Leonard Lu updated TAP5-931:
----------------------------
Attachment: Test.java
Example component class that demonstrates this bug is attached.
> Component Parameters not always persisted to the end of a Heartbeat
> -------------------------------------------------------------------
>
> Key: TAP5-931
> URL: https://issues.apache.org/jira/browse/TAP5-931
> Project: Tapestry 5
> Issue Type: Bug
> Components: tapestry-core
> Affects Versions: 5.1.0.5
> Reporter: Leonard Lu
> Priority: Minor
> Attachments: Test.java
>
>
> Odd bug. In the component class that I will attach after creating this Issue,
> a parameter of type JSONObject is bound and modified during page render, then
> deferred to the end of a Heartbeat. In some circumstances when the deferred
> command is run, the parameter is recreated from the bound property and the
> earlier changes are lost.
> Circumstances when an error occurs:
> 1) The parameter is bound to an empty JSONObject, either new JSONObject(), or
> new JSONObject("{}")
> 2) The parameter is given a default value of an empty JSONObject
> Circumstances when an error does not occur:
> 1) The parameter is bound to a populated JSONObject (e.g. new
> JSONObject("{property:'value'}"))
> 2) The parameter is bound to any literal that is coerced to a JSONObject
> 3) A reference to the parameter is saved in a different final variable that
> is passed into the Runnable command.
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
