Fair point, at least as far as params go :) I never noticed the getParameterMap() method to be honest.
The methods in RequestUtils (and the one in SessionUtils) came from the fact that during debugging I (and I think most of us) have a need to easily see what's coming in with a request. So, I wind up doing the following in Actions and/or JSPs with these methods: log.debug(RequestUtils.getAllRequestInfo(request)); (getAllRequestInfo calls the other three methods to get parameters, attributes and headers). It's certainly not rocket science or anything, I certainly never claimed these functions were the savior of the world or anything :) but it's a nice and easy way to see what's going on (I do my development in Tomcat, so I simply glance over to my second monitor in the console window to see the output in real-time). -- Frank W. Zammetti Founder and Chief Software Architect Omnytex Technologies http://www.omnytex.com On Mon, May 2, 2005 10:37 am, Dave Newton said: > Frank W. Zammetti wrote: > >> Alternatively, you could use the Commons Servlet packages' >> getRequestParameter(), getRequestHeaders() and getRequestAttributes() >> methods of the RequestUtils class, and if you need it there is also a >> getSessionAttributes() method in SessionUtils (I know because I added >> all four!) >> >> http://svn.apache.org/viewcvs.cgi/jakarta/commons/sandbox/servlet/ > > I think I'm probably missing something here, but it looks like this > takes the parameters or attributes of the request and puts them into a > hash. Is this just to decouple it from the ServletRequest? For > parameters, at least, isn't there already a method that returns the map? > > Dave > > > > --------------------------------------------------------------------- > 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]
