Nightly Builds

06-07-2006, 12:53 AM

Here's the code fragment to enumerate the request parameters list, but
the order
is not the same as in the query string.

http://localhost:9999/projWeb/EStore...=1&b=2&c=3&d=4

==========================
Code
==========================
for (Enumeration e = req.getParameterNames(); e.hasMoreElements()

{ Object obj = e.nextElement();
String key = obj.toString();
String value = req.getParameter(key);
out.println(key + "," + value + "
");
}

==========================
output
===========================
b,2
a,1
sub,Logon
d,4
c,3

any ideas?

please advise. thanks!!
John.

John

06-07-2006, 01:28 PM

"John" <> wrote in message
news: oups.com...
> Here's the code fragment to enumerate the request parameters list, but
> the order
> is not the same as in the query string.
>
> http://localhost:9999/projWeb/EStore...=1&b=2&c=3&d=4
>

The parameters are name-value pairs without any presumption of order. They
are probably stored in a HashMap and the enumeration order depends on the
hashing. I tried your code and the parameters came back in mixed order for
JBoss 4.0.2.

I searched through various javadocs and could not find anything that says
the parameters should be retrievable in their original order. If your
design relies on parameter order, something is going to have to change.
Also, I don't think there's any guarantee that forms or other external
sources will put the parameters in the textual order given, or that URL
transforms (URL rewriting) will preserve the order.

If you can't change the design, you can retrieve the original query string
(getQueryString) and pick off the parameters yourself. There are some
libraries to do this, although I don't know their names. Especially for POST
requests, reading the body as a stream may interfere with the ability to
read the names in order.

Cheers,
Matt Humphrey http://www.iviz.com/

06-07-2006, 07:10 PM

John wrote:
> Here's the code fragment to enumerate the request parameters list, but
> the order
> is not the same as in the query string.
>
>
>

>
> any ideas?
>
> please advise. thanks!!
> John.
>

The order is not guaranteed and can be affected by the the sending client and
the receiving server.

Why do you need to read the parameters in a specific order ?

If you need to do that then you will have to do the ordering yourself, possibly
by appending a number to the parameter name to give the order,

i.e.

http://localhost:9999/projWeb/EStore...am3=3&param4=4

and then parsing this using the know prefix 'param'.

06-08-2006, 03:34 AM

On Wed, 07 Jun 2006 18:10:31 +0000, Andy Flowers wrote:

> John wrote:
>> Here's the code fragment to enumerate the request parameters list, but
>> the order
>> is not the same as in the query string.
>>
>>
>>
>
>>
>> any ideas?
>>
>> please advise. thanks!!
>> John.
>>
>
> The order is not guaranteed and can be affected by the the sending client and
> the receiving server.

No, only by the receiving server. According to the HTTP and URL/URI
specifications the URLs

http://www.example.com/someapp/servlet?a=foo&b=bar
and
http://www.example.com/someapp/servlet?b=bar&a=foo

are distinct resources. The Java servlet specification allows the
servlet container to reorder request parameters because in practice those
are more often the same resource with two names than two distinct
resources, and storing the parsed parameters in a hashmap is far faster
than seeking through them in order.

IMO parameters should probably be provided in a LinkedMap or LinkedHashMap
stored in URL order, because there are some useful idioms based on
multiple occurrences of the same parameter, but I haven't written a
servlet container or plugin, so my opinion's worth the electrons to print
it and not a bit more.

Owen

06-08-2006, 05:47 PM

Owen Jacobson wrote:
> IMO parameters should probably be provided in a LinkedMap or LinkedHashMap
> stored in URL order, because there are some useful idioms based on
> multiple occurrences of the same parameter, but I haven't written a
> servlet container or plugin, so my opinion's worth the electrons to print
> it and not a bit more.

At least in Tomcat my experience has been that repeated parameters are
always returned in order. I.e. using getParametervalues() with:

http://www.example.com/someapp/servlet?a=X&a=Y&x=Z

returns an array in the "natural" order. I agree this is a useful idiom
and could be a solution for the OP, but I don't see it guaranteed
anywhere in the spec.

HT

06-07-2006, 01:28 PM	#2
Matt Humphrey Posts: n/a	Re: get request parameters are not in order "John" <> wrote in message news: oups.com... > Here's the code fragment to enumerate the request parameters list, but > the order > is not the same as in the query string. > > http://localhost:9999/projWeb/EStore...=1&b=2&c=3&d=4 > The parameters are name-value pairs without any presumption of order. They are probably stored in a HashMap and the enumeration order depends on the hashing. I tried your code and the parameters came back in mixed order for JBoss 4.0.2. I searched through various javadocs and could not find anything that says the parameters should be retrievable in their original order. If your design relies on parameter order, something is going to have to change. Also, I don't think there's any guarantee that forms or other external sources will put the parameters in the textual order given, or that URL transforms (URL rewriting) will preserve the order. If you can't change the design, you can retrieve the original query string (getQueryString) and pick off the parameters yourself. There are some libraries to do this, although I don't know their names. Especially for POST requests, reading the body as a stream may interfere with the ability to read the names in order. Cheers, Matt Humphrey http://www.iviz.com/

06-07-2006, 07:10 PM	#3
Andy Flowers Posts: n/a	Re: get request parameters are not in order John wrote: > Here's the code fragment to enumerate the request parameters list, but > the order > is not the same as in the query string. > > > > > any ideas? > > please advise. thanks!! > John. > The order is not guaranteed and can be affected by the the sending client and the receiving server. Why do you need to read the parameters in a specific order ? If you need to do that then you will have to do the ordering yourself, possibly by appending a number to the parameter name to give the order, i.e. http://localhost:9999/projWeb/EStore...am3=3&param4=4 and then parsing this using the know prefix 'param'.

06-08-2006, 03:34 AM	#4
Owen Jacobson Posts: n/a	Re: get request parameters are not in order On Wed, 07 Jun 2006 18:10:31 +0000, Andy Flowers wrote: > John wrote: >> Here's the code fragment to enumerate the request parameters list, but >> the order >> is not the same as in the query string. >> >> >> > >> >> any ideas? >> >> please advise. thanks!! >> John. >> > > The order is not guaranteed and can be affected by the the sending client and > the receiving server. No, only by the receiving server. According to the HTTP and URL/URI specifications the URLs http://www.example.com/someapp/servlet?a=foo&b=bar and http://www.example.com/someapp/servlet?b=bar&a=foo are distinct resources. The Java servlet specification allows the servlet container to reorder request parameters because in practice those are more often the same resource with two names than two distinct resources, and storing the parsed parameters in a hashmap is far faster than seeking through them in order. IMO parameters should probably be provided in a LinkedMap or LinkedHashMap stored in URL order, because there are some useful idioms based on multiple occurrences of the same parameter, but I haven't written a servlet container or plugin, so my opinion's worth the electrons to print it and not a bit more. Owen

06-08-2006, 05:47 PM	#5
Henry Townsend Posts: n/a	Re: get request parameters are not in order Owen Jacobson wrote: > IMO parameters should probably be provided in a LinkedMap or LinkedHashMap > stored in URL order, because there are some useful idioms based on > multiple occurrences of the same parameter, but I haven't written a > servlet container or plugin, so my opinion's worth the electrons to print > it and not a bit more. At least in Tomcat my experience has been that repeated parameters are always returned in order. I.e. using getParametervalues() with: http://www.example.com/someapp/servlet?a=X&a=Y&x=Z returns an array in the "natural" order. I agree this is a useful idiom and could be a solution for the OP, but I don't see it guaranteed anywhere in the spec. HT

Nightly Builds

Saturday, October 8, 2011

Clojure Presentation

Tuesday, August 5, 2008

Nasty JVM error

Tuesday, July 29, 2008

JavaScript - The features I never knew

Thursday, July 10, 2008

Spring Configuration Issue - How to specify path to config file

Saturday, March 1, 2008

Steps in Making use of a Tag Library Validator

Validation error messages from TagLibraryValidator for Tag library descriptor in /parser.jsp

null: JSP page contains 2 scriptlets.

Thursday, February 28, 2008

Observation: Stupid fact

Java - get request parameters are not in order

Saturday, February 16, 2008

Eclipse, Apache Tomcat, Servlets

Subscribe To My Podcast

Blog Archive

About Me

Traffic Feed

06-07-2006, 12:53 AM	#1
	get request parameters are not in order Here's the code fragment to enumerate the request parameters list, but the order is not the same as in the query string. http://localhost:9999/projWeb/EStore...=1&b=2&c=3&d=4 ========================== Code ========================== for (Enumeration e = req.getParameterNames(); e.hasMoreElements() { Object obj = e.nextElement(); String key = obj.toString(); String value = req.getParameter(key); out.println(key + "," + value + " "); } ========================== output =========================== b,2 a,1 sub,Logon d,4 c,3 any ideas? please advise. thanks!! John. John