If the form is used to create other output (like eMail) it is reasonable to reproduce the order of the fields.
In this case it can be desired that the eMail reflects the changes that where made to the form. In this scenario the servlet wouldn't be less reliable, as it's not the inner logic that depens on the order of the attributes, just the result will be different if you change the form. > -----Urspr�ngliche Nachricht----- > Von: Tom Drake [mailto:[EMAIL PROTECTED]] > Gesendet: Dienstag, 18. Dezember 2001 00:58 > An: Tomcat Users List > Betreff: Re: Ordering of parameters in HTTPRequest Object > > > 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 -- To unsubscribe: <mailto:[EMAIL PROTECTED]> For additional commands: <mailto:[EMAIL PROTECTED]> Troubles with the list: <mailto:[EMAIL PROTECTED]>
