> well, its still messy unless you override map.put and wrap things that are > not an array in one.
Blame the servlet API for that. I don't think we should 'fix' their bad choice (as yes, what we had was indeed nicer, but just inconsistent and because of that got people into trouble). It sounds like we're still running around in circles though. The fix was there for a reason. I don't know the exact thing from the top of my head, but I didn't go in there spontaneously. There were reports and a fix if I remember correctly, and just looking at the consistency between what we returned and the servlet API returned, I think it is pretty clear it was bad we decided to deviate. If there are any problems resulting from this change now, we should fix *those*. I asked *several* times for reproducable cases and unit tests, as we had no unit tests that fail because of the change, and neither did any of the example applications fails. If we have tests, fixes should be easy no? And they would hopefully stay fixed. Eelco ------------------------------------------------------------------------- This SF.net email is sponsored by DB2 Express Download DB2 Express C - the FREE version of DB2 express and take control of your XML. No limits. Just data. Click to get it now. http://sourceforge.net/powerbar/db2/ _______________________________________________ Wicket-user mailing list Wicket-user@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/wicket-user
