It works. Thank you very much
--
View this message in context:
http://apache-wicket.1842946.n4.nabble.com/user-interface-design-if-any-error-textbox-channge-to-red-tp4659495p4659797.html
Sent from the Users forum mailing list archive at Nabble.com.
Hi Joachim,
On Sat, Jun 15, 2013 at 3:15 AM, Joachim Schrod jsch...@acm.org wrote:
Bas Gooren wrote:
To only update the attribute if the component has errors, override
method isEnabled on the behavior, cast the component to a
FormComponent and return !formComponent.isValid().
And
Thanks a lot.
I will try it on weekend.
--
View this message in context:
http://apache-wicket.1842946.n4.nabble.com/user-interface-design-if-any-error-textbox-channge-to-red-tp4659495p4659522.html
Sent from the Users forum mailing list archive at Nabble.com.
Also you can pass as second argument in AttributeModifier IModel object
which return error on if there feedback message available.
Similar to this:
new AttributeModifier(class, new Model() {
@Override
public Serializable getObject() {
Hi!
Feedback messages are cleanup up (removed) after each request.
The attribute modified you added to the component, remains in place if
the page is stateful.
That's why the field still has the error class after a reload.
You can do a number of things to make this work, but the essence is
Bas Gooren wrote:
To only update the attribute if the component has errors, override
method isEnabled on the behavior, cast the component to a
FormComponent and return !formComponent.isValid().
And remember that you must not use isValid() in onComponentTag() to
change tag attributes. You
