So I have a page which is basically just updating three persisted variables. (Code below). One is being updated when a user changes selection on a <select> input (selectedNode). One is a string when a user enters text in a simple text field (nodeNameValue). The last is a string I am manipulating in the code (parentPath).
The select and parentPath are in a zone so when the user changes the select it updates both. This works fine and when setting a breakpoint in the onValueChanged I can see all 3 variables hold what I expect. The problem is when I click the submit button selectedNode is null and all the others are exactly as I would expect. This is an application written with Tapestry 5.3.2. I am thinking its some odd behavior from the Zone? Probably not a bug just that I am doing something wrong. I have put in a work around (hack) but would really like to understand what my mistake is. TML: Java: For the GenericSelectModel The source can be found: http://jumpstart.doublenegative.com.au/jumpstart/examples/select/easyobject -- View this message in context: http://tapestry.1045711.n5.nabble.com/Persist-variable-being-lost-tp5551835p5551835.html Sent from the Tapestry - User mailing list archive at Nabble.com. --------------------------------------------------------------------- To unsubscribe, e-mail: users-unsubscr...@tapestry.apache.org For additional commands, e-mail: users-h...@tapestry.apache.org
