This may be a dumb question, but do you really care about the order of the form parameters?
It seems to me that making your servlet / jsp dependant on the order of the parameters is a huge mistake, even if this order is guaranteed by all browsers and by Tomcat and all other servlet containers. The problem is that your servlet that processes the request will be tied to the gui layout of the form. If the gui designer decides to lay the form out in a different way next week, your code will break. IMHO, your solution would be far more robust if it relied on the names of the parameters, and not the order in which they're received. Tom Drake ----- Original Message ----- From: "Christopher K. St. John" <[EMAIL PROTECTED]> To: "Tomcat Users List" <[EMAIL PROTECTED]> Sent: Monday, December 17, 2001 4:33 PM Subject: Re: Ordering of parameters in HTTPRequest Object | "Craig R. McClanahan" wrote: | > | > There are no guarantees that a browser will send the | > request parameters in the order they appear on the form | > | | http://www.w3.org/TR/html4/interact/forms.html#h-17.13.4.1 | | application/x-www-form-urlencoded | | This is the default content type. Forms submitted with | this content type must be encoded as follows: | | 1. Control names and values are escaped ... | | 2. The control names/values are listed in the order they | appear in the document. ... | | That's just for urlencoded forms, but then again that's | the only content-type the servlet spec makes any | promises about. | | It seems reasonable that a servlet container should | return the params in order for content-types where | the ordering is guaranteed. | | -- | Christopher St. John [EMAIL PROTECTED] | DistribuTopia http://www.distributopia.com | | -- | To unsubscribe: <mailto:[EMAIL PROTECTED]> | For additional commands: <mailto:[EMAIL PROTECTED]> | Troubles with the list: <mailto:[EMAIL PROTECTED]> | | | -- To unsubscribe: <mailto:[EMAIL PROTECTED]> For additional commands: <mailto:[EMAIL PROTECTED]> Troubles with the list: <mailto:[EMAIL PROTECTED]>
