I could use both model or onSubmit to do what I mentioned. But this resulted in repeating coding. If I put the special conversion code in converter, it would be handily reusable by me or others without worring about the convertion logic for each model or form. Validator chaining is the example of what I meant
>i think a model decorator is more appropriate here > >-igor > > >On Sat, Mar 8, 2008 at 3:10 PM, <[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]
