Hi, Johan, Thanks for the explanation, it helps understanding why it happens... but it does not happen always...
I guess there's some kind of contradiction here, as I have detected this behaviour at my work-code, but not at my home-code, mentioned some e-mails before (a very simple sample). So, depending on some unknown conditions it behaves doing the expected string2string conversion, and depending some others it does the string2string[1] conversion. Now the point for me is, what to do next? I will try the patch already quoted... but, is that the solution to this issue or should I resign myself accepting those string2string[1] conversions, as I am temporary accepting right now? Thanks On 5/14/07, Johan Compagner <[EMAIL PROTECTED]> wrote: > the String arrays come from the change eelco did in the ServletWebRequest: > public Map getParameterMap() > { > // Lazy-init parameter map. Only make one copy. It's more efficient, > and > // we can add stuff to it (which the BookmarkablePage stuff does). > if (parameterMap == null) > { > parameterMap = new > HashMap(httpServletRequest.getParameterMap()); > } > // return a mutable copy > return parameterMap; > } > > we now just make a copy > before this code didn't make only a copy but also tested if the parameter > was a String[].length > 1 > then it kept the string array, if not then it only did store the first > element.. > > johan > > > > On 5/14/07, Jean-Baptiste Quenot <[EMAIL PROTECTED]> wrote: > > * manuel barzi: > > > > > Unfortunatelly, I have to confirm you this is actually not true > > > in 1.2.6 (I guess the link provided by Jean-Baptiste Quenot is > > > explaining it all). > > > > > > In my case I just transfer independent > key-values (never > > > repeated), and when recovering them at the parameters > > > receiver-page, I have to cast to String[], and all of them are > > > of the size 1. So, really, what's happening inside is a String > > > to String[1] conversion. Which is not actually following the > > > mentioned spec. > > > > You may want to try the patch attached to the Jira issue. But > > note that this is a workaround, not really a solution to the > > problem as I don't know where those String arrays come from. > > -- > > Jean-Baptiste Quenot > > aka John Banana Qwerty > > http://caraldi.com/jbq/ > > > > > ------------------------------------------------------------------------- > > 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 > > > > > ------------------------------------------------------------------------- > 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 > > ------------------------------------------------------------------------- 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