Hey Dude, I was certainly not trying to be arbitrary . . . If Iplanet is more "robust" in this area don't take it personally. As far as your sour memory in DB development, please leave me out of it. This was a simple question that makes a lot of sense when you are building any web applications. If there is a problem with the specification, then it should be changed to accommodate the user. Tomcat or any other software of that sort are loaded with functions/features that sacrifice performance with functionality, this is what you call "an option".
Jeff Grangier -----Original Message----- From: George Sexton [mailto:[EMAIL PROTECTED] Sent: Friday, August 12, 2005 1:46 PM To: 'Tomcat Users List' Subject: RE: Tomcat and the HttpServletRequest Object Even if I were to write this as an enhancement, I can tell you from past experience it would be rejected out of hand by the committers. In your particular case, the tool you were using before used something like a Vector or ArrayList to hold the parameter name/value pairs. Tomcat is almost certainly using a HashMap of some sort. Any deterministic implementation is going to be slower than the current random access implementation. Committers will savage any submission that appears slower and the person submitting it. No thanks, I'm not going there. Even if Tomcat were to work in the manner desired, there's nothing that says that every browser is going to submit the form elements in their order of definition. You really need to abandon this idea and make your application more robust. You remind me of people who do SQL database development. They don't specify an ORDER BY clause on their statements, but it always came back in the order they wanted. Then one day, they upgraded versions of the database or the query optimizer decided to take a different path, and all of a sudden the results are coming out of order. Much wailing and attempted reporting of bugs ensues... The truth is in SQL, that if you don't specify an ORDER BY clause, the database can return the results in any order it likes. Taking advantage of an implementation specific behavior is natural, but it can lead (as you have found out) to non-portable code. The final arbiter is the specification, and if the specification doesn't describe the behavior, you can't say anything about it. George Sexton MH Software, Inc. http://www.mhsoftware.com/ Voice: 303 438 9585 > -----Original Message----- > From: Jeff Grangier [mailto:[EMAIL PROTECTED] > Sent: Friday, August 12, 2005 12:19 PM > To: 'Tomcat Users List' > Subject: RE: Tomcat and the HttpServletRequest Object > > Hello George, > > I will consider it an ehancement if it is not in the > specification. Adding a > logical order to the list makes it much easier to manage dynamically. > Otherwize, any programmer will have to create their own > proprietary indexing > and ordering logic for it. > > Let me know if I can help in this upgrade? > > Thanks, > Jeff > > > -----Original Message----- > From: George Sexton [mailto:[EMAIL PROTECTED] > Sent: Friday, August 12, 2005 12:40 PM > To: 'Tomcat Users List' > Subject: RE: Tomcat and the HttpServletRequest Object > > I see nothing in the specification that specifies the order > of the elements > returned in the enumeration. > > Why do you think this is a bug? > > > George Sexton > MH Software, Inc. > http://www.mhsoftware.com/ > Voice: 303 438 9585 > > > > -----Original Message----- > > From: Jeff Grangier [mailto:[EMAIL PROTECTED] > > Sent: Friday, August 12, 2005 11:22 AM > > To: tomcat-user@jakarta.apache.org > > Subject: Tomcat and the HttpServletRequest Object > > > > > > > > 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] > > > > --------------------------------------------------------------------- > To unsubscribe, e-mail: [EMAIL PROTECTED] > For additional commands, e-mail: [EMAIL PROTECTED] > > --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED] --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
