Mailing-List: contact tomcat-dev-help@jakarta.apache.org; run by ezmlm
Precedence: bulk
Reply-To: "Tomcat Developers List" <tomcat-dev@jakarta.apache.org>
Message-ID: <3F841EA7.3080505@joedog.org>
Date: Wed, 08 Oct 2003 10:26:47 -0400
From: Tim Funk <funkman@joedog.org>
Organization: Human being
User-Agent: Mozilla/5.0 (Windows; U; Windows NT 5.0; en-US;
 rv:1.4) Gecko/20030624
MIME-Version: 1.0
To: Tomcat Developers List <tomcat-dev@jakarta.apache.org>
Subject: Re: Order of parameters
References: <61BAD406AA642745AE1142AF689E8D8E030B27@madocontrol.madocke.local>
In-Reply-To: 
 <61BAD406AA642745AE1142AF689E8D8E030B27@madocontrol.madocke.local>
Content-Type: text/plain; charset=us-ascii; format=flowed
Content-Transfer-Encoding: 7bit

The problem lies in the servlet spec. It does not dictate that 
request.getParameterNames() returns the parameter list in any specific order. 
A feature request to the spec working group is your best bet. If your using 
GET - you always have access to the query string and a "simple regex" can 
return your parameter list.

-Tim

Martin van Dijken wrote:
>>The solution is to pass a fields list as an additional 
>>paramter, and use
>>that field list to drive the ordering of your form.
> 
> 
> That is of course possible, but requires more code in the form, which is in my opinion totally unnecessary. ASP, and I think PHP as well, have this as one of their most basic features, so I really don't see why Tomcat shouldn't.
> 


---------------------------------------------------------------------
To unsubscribe, e-mail: tomcat-dev-unsubscribe@jakarta.apache.org
For additional commands, e-mail: tomcat-dev-help@jakarta.apache.org