[GROOVY-3939] @Bindable with validator allows incorrect behaviour on binding creation

• Type: Bug
• Status: Closed
• Priority: Major
• Resolution: Fixed
• Affects Version/s: 1.7-rc-2
• Fix Version/s: 1.8.1
• Environment: Actually saw this in Griffon 0.3 snapshot, but is a @Bindable issue
• Assignee: Andres Almiray
• Reporter: alpheratz
• Created: 14/Dec/09 00:24
• Updated: 19/Aug/11 21:36
• Resolved: 19/Aug/11 11:24

Description

Currently a binding's validator only reacts to a change and is not given a chance to react to any initial data.

Given:

Model:

@Bindable String data = 'x'

View:

textField(id: 'port', columns: 5, text: bind(source: model, 'port',
mutual: true, validator: { isInteger(port) }))

As created, the textField will contain 'x', even though an isInteger validator method (assuming one exists and is correct) would reject it. If 'y' is subsequently typed into the field, the validator will run and will (presumably)reject the contents.

More discussion and workaround here: http://archive.codehaus.org/lists/org.codehaus.griffon.user/msg/001701ca7885$a4925f40$edb71dc0$@com.au