> in 1.1 you must have had a formid.fieldid.TypeValidator key > this same key should still work in 1.2
Sorry if I confused you. I was trying to say that no, I did NOT have any such key in 1.1. I did not use any type of validator, and no exception was thrown like it is now in 1.2. > in fact TypeValidator key would also work in 1.1, see > http://www.wicket-wiki.org.uk/wiki/index.php/Validation_Messages Ok, that's all good to know. This is the first time I've had to deal with it, since I didn't seem to require it in 1.1. > afaik the transition should have been seamless as we did not change > this part of wicket. Probably, you thought that I was using validation in 1.1. If I were, then the transition would surely have been seamless. I think that what's different is that I wasn't using validation in 1.1 (no problems), but now in 1.2, suddenly validation is required in this circumstance. Does that make sense? > i am wondering why it wasnt, can you provide more details? Essentially, this is what I was doing: final TextField queryExpressionField = new TextField( "freeExpressionField", m_freeExpressionModel, QueryExpression.class ) { public IConverter getConverter() { return new QueryExpressionConverter(); } }; add( queryExpressionField ); As I said, this worked fine in 1.1 without any validation. When suddenly I was getting exceptions in 1.2, this confused me. Thanks for all the help. Let me know if you'd like me to add something to the 1.2 migration list. ------------------------------------------------------- This SF.net email is sponsored by: Splunk Inc. Do you grep through log files for problems? Stop! Download the new AJAX search engine that makes searching your log files as easy as surfing the web. DOWNLOAD SPLUNK! http://sel.as-us.falkag.net/sel?cmd=lnk&kid=103432&bid=230486&dat=121642 _______________________________________________ Wicket-user mailing list [email protected] https://lists.sourceforge.net/lists/listinfo/wicket-user
