I have the following composite component (
You need to register it as client behavior in composite's interface.
...
...
name
: The custom event name as you would specify in composite's client. Can be the same as the actual event name. Can be a customized one. It's all free to your choice.targets
: The composite implementation relative client ID of the target component on which the actual client behavior should be attached.event
: The actual event name which the actual client behavior should be listening. Note that the default event of EditableValueHolder
components is valueChange
and not change
. You can for text input fields keep using change
if you want.With the above declaration example, you can use it in template client as below:
After this, you'll face a second but unrelated problem which is already asked and answered here:
Unrelated to the concrete problem, that composite can better be a tagfile. And, that HTML table markup is not Web 2.0.