[
https://issues.apache.org/jira/browse/TAP5-1527?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13049167#comment-13049167
]
Geoff Callender commented on TAP5-1527:
---------------------------------------
I've modified
http://jumpstart.doublenegative.com.au/jumpstart/examples/input/edit1/1 to work
around this bug - it now gets the object in setupRender if the object is null.
> BeanEditForm loses object found by onPrepare() during render
> ------------------------------------------------------------
>
> Key: TAP5-1527
> URL: https://issues.apache.org/jira/browse/TAP5-1527
> Project: Tapestry 5
> Issue Type: Bug
> Components: tapestry-core
> Affects Versions: 5.2.5
> Reporter: Geoff Callender
> Priority: Critical
>
> Was fine in 5.1.0.5, discovered when upgrading to 5.2.5.
> Using a BeanEditForm to edit an object: onPrepare() is being called twice (!)
> during the render phase, and then the object found in onPrepare() disappears!
> http://jumpstart.doublenegative.com.au/jumpstart/examples/input/edit1/1
> Yet, when you replace BeanEditForm with a Form around a BeanEditor,
> everything works correctly: onPrepare() is called once during the render
> phase and the object doesn't disappear:
>
> http://jumpstart.doublenegative.com.au/jumpstart/examples/input/morecontroledit1/1
> You can see the java code is almost identical in the two examples but the
> result is different.
> For more discussion see
> http://tapestry.1045711.n5.nabble.com/BeanEditForm-What-s-happening-to-my-object-parameter-tt4257173.html#none
> .
--
This message is automatically generated by JIRA.
For more information on JIRA, see: http://www.atlassian.com/software/jira
