Thanks. I will give a try, although I wish there would be something like
component.add(IPostConverteToObject or IPostConverttoString) that would
not require subclass and also allow easy reuse of what is available.
A related question, after conversion is done, Can I do something like below
class MyTextField extend TextField{
@Override
setModel(model){
MySpeicalProcessing(model) // after this model object is changed to what I
want
super.setModel(model)
}
}
The javadoc said it
WARNING: DO NOT OVERRIDE THIS METHOD UNLESS YOU HAVE A VERY GOOD REASON FOR IT.
OVERRIDING THIS MIGHT OPEN UP SECURITY LEAKS AND BREAK BACK-BUTTON SUPPORT.
Also, would wicket gurantee that after the conversion, it would only call
setModel(model) instead of being able to use other means to update the model
value
such as setModelObject. If allowed, then the above method could fail
mysteriously.
Thanks
>Override the getConverter() method. First call super and with that
>result call the special one (camel casing?)
>
>On 3/9/08, [EMAIL PROTECTED] <[EMAIL PROTECTED]> wrote:
>> Hello:
>> I wonder how to "append" a converter or java method to a component so that
>I
>> would affect what is already defined. For example, I want "camelize" a
>> TextField(or some customized subclass) so that after the converter already
>> defined completes the conversion (regardless what has been done in the
>> chain) , I could use the added converted/method to make the final
>conversion
>> to my need. The example I am seeing appears to "overide" and only one can
>be
>> defined for a component, unlike validators, that I could add a chain of
>> them. Let me know if I am wrong about this.
>> Thanks
>
>---------------------------------------------------------------------
>To unsubscribe, e-mail: [EMAIL PROTECTED]
>For additional commands, e-mail: [EMAIL PROTECTED]
>
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
