Hi Martin! > Well, the thing is that a merge is way off on the timeline. > And Cagatay has something right now, why not take it in? No, I didnt meant to NOT take Cagatys work now. In fact I'd love to see it imported soon. Its just the converter stuff I was thinking about.
But now I also think we should put our hands on the converter stuff, just, as far as I can see, in Trinidad they implemented a real client validator with getAsObject and getAsString - to say the truth, I dont like this. If we say a converter has also a role as validator (I dont like this idea too, but its by their nature that they do validation) I would love to see them simply use the same ClientValidator interface than the normal validator - On client side we just would like to validate and NOT to convert in first place. Later, when we see that we really need a client side converter we can implement this stuff too, we dont need it for date and number converter, the possibility to check onkeypress is much more important. I think the client side converter approach isnt really that usable - how do you convert a complex (maybe serialized) java object? So +1 for allowing the ClientValidator interface on the converter too. Ciao, Mario
