submitMonitor.for property generated getter/setter EL evaluation wasn't working since it was using forVal.name() which is "forVal" as the name() method is the enum's name and not the annotation's name.

This means that all of the components with for properties were not working if tied to ValueExpressions, they would just return null, or possibly whatever their default value was.

This is the list, along with their unaliased names from the Meta classes:

contextMenu.forValue
draggable.forValue
droppable.forValue
message.forValue
messages.forValue
printer.forValue
resizable.forValue
submitMonitor.For
tableConfigPanel.forTarget
tabSetProxy.For
tooltip.forValue

QA reproduced the EL value being null with several of the components from the list, and confirmed the fix after the generator fix commit.

icefaces3 trunk
Subversion 33476

There were interactions between ICE-8965 and ICE-9844, where onElementUpdate not cleaning up the submitMonitor allowed it to appear to work in some cases where the new create code was not initialising due to a lingering widgetVar. So having the cleanup code ran appeared to break things. This made it appear that it was using the old cfg.monitorFor value from the last page refresh.

Tweaked the showcase sample to add a delay to the input elements in the configuration panel, so if they cause a submit then it will last longer, like the Submit button in the demonstration panel, to better illustrate the submitMonitor.

icefaces3 trunk
Subversion 33544

Tested, and shown to be fixed by ICE-8965.