Valid())
But i guess this is not that logical to do (know)
clearInput can be public final in my eyes.
johan
On 5/9/06, Roan O'Sullivan < [EMAIL PROTECTED]> wrote:
Could the FormComponent#clearInput() be made public?
This is my scenario:
Could the FormComponent#clearInput() be made public?
This is my scenario:
* a recipient property on my model object
* a DropDown (that listens to selection change events) lets users select from a list of Recipient beans
* a TextField is bound to the email field for the model object's reci
I get the same exception. Here is the stack trace:
java.lang.NullPointerException
at
wicket.PageMap.visitEntries(Lwicket.PageMap$IVisitor;)V(PageMap.java:574)
at wicket.PageMap.clear()V(PageMap.java:193)
at wicket.PageMap.remove()V(PageMap.java:308)
at
wicket.Ses
Thanks for your responses Igor.
I was thinking in terms of AttributeModifiers b/c still using 1.1.1, but
"Component#setEnabled(false)" in 1.2 should satisfy my current requirements.
Looking forward to the official 1.2 release.
-- Roan
From: [EMAIL PROTECTE
n must take care
of back button also so that has to be versioned.
johan
On 4/26/06, Roan O'Sullivan <[EMAIL PROTECTED]> wrote:
This is certainly a better workaround than re-instantiating the
component... thanks.
But I'm still curious, is there
mpound.add(YYYValidator);
compound.validate()
{
iterator.next().validate()
}
component.add(compound);
compound.remove(xxx);
johan
On 4/25/06, Roan O'Sullivan <[EMAIL PROTECTED] > wrote:
Hi Igor,
I have this same requirement, also in the con
4/25/06, Roan O'Sullivan < [EMAIL PROTECTED] <mailto:[EMAIL PROTECTED]> >
wrote:
Hi Igor,
I have this same requirement, also in the context of dynamic forms.
I think a simple #removeAllValidators() would do the trick without
introducing
Hi Igor,
I have this same requirement, also in the context of dynamic forms.
I think a simple #removeAllValidators() would do the trick without introducing
ambiguity or any additional complexity. In v1.1.1 I end up reconstructing the
component when, for example, I need to remove a TypeValid
Thanks Igor. ListView.setUseOptimizedItemRemoval(true) does the trick. Now that
I know about this behavior, I find the Javadocs do a good job of filling in the
details.
From: [EMAIL PROTECTED] on behalf of Roan O'Sullivan
Sent: Thu 3/30/2006 8:50
On 3/29/06, Roan O'Sullivan <[EMAIL PROTECTED] > wrote:
Hi.I am dynamically building a form, and I dynamically add validators
for TextField inputs (RequiredValidator, TypeValidator, etc.) in a
DropDownChoice's IOnChangeListener method. When I step through the code, tha
Hi.I am dynamically
building a form, and I dynamically add validators for TextField inputs
(RequiredValidator, TypeValidator, etc.) in a DropDownChoice's
IOnChangeListener method. When I step through the code, that seems to work
correctly: validators are added to the TextField input.
But whe
Thanks for all the work guys. Really enjoying the framework
so far.
I would like to define a layout using an
abstract WebPage called TemplatePage (using Markup Inheritance as per the
wiki and the Templating example in wicket-examples), but implement the template
using a frameset. I want the m
12 matches
Mail list logo
