I checked and getting correct order as displayed, but it seems completely depends on browser. If browser sents in different order then my business logic will crash.
Its actually not to check the value.
It will update the DB with the data for coresponding key. so based on the index i will form the query string, so if the order changes then wrong data will be updated for the wrong row in the db.
Form elements are normally submitted in the order defined--but you'd have to check the spec to see if this is enforced by the spec. Even then, like you, I'd be nervous about depending on the browser to always do the right thing. Personally I'd consider using an indexed notation.
Not using a framework that handles things like this automatically makes for extra work. You might be able to use an existing EL implementation to make things easier, but I've never actually tried using one outside of a framework that already supports it.
David Newton wrote:Form elements are normally submitted in the order defined--but you'd have to check the spec to see if this is enforced by the spec.
It is not.
A framework isn't really needed. Using indexed notation means that it'd be easy to use normal bean injection into indexed properties. For example, the Jakarata Commons BeanUtils utility class will handle indexed properties nicely.