I have the same bloody problem. The application is a generic form handler that
e-mails the form values. Most (all) of the clients expect the values to be in
the same order as the form itself.
I question the requirement to improve performance on request parameters. Vast
majority of the requests have less than 50 parameters and I fail to see how
changing a collection would improve performance. It might improve performance a
little bit when there's hundreds or thousands of parameters but not when it's
less than 50.
I noticed that SunOne 6.0 web server had the same problem when they embedded
Catalina in it. But they at least fixed the problem in subsequent releases (6.1
and above) when we complained about it. It makes you wonder - if Sun can fix
the problem even though performance requirements on SunOne servers are
significantly higher than tomcat because they are selling the product for
profit, why tomcat community would not do the same and make life easier for us
developers.
--
Bhupinder
On 12/08/2005 11:22 AM, Jeff Grangier wrote:
Hello,
I have migrated my application from iPlanet to Tomcat 5.5 (latest build as
of today) and getting weird results with the HttpServletRequest object:
Each Element out the getParameterNames enumeration used to be ordered based
on the html form layout posting the data (using iPLanet). But, after the
migration the fields are coming in random order when I try to loop through
the fields dynamically. . .
Here is a snapshot of the code:
Enumeration paramNames = req.getParameterNames();
while(paramNames.hasMoreElements())
{
paramName = (String)paramNames.nextElement();
.
.
.
Has anyone encountered this issue before? Is there a work around?
Thank you in advance for your help,
Jeff
-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
