Big RequestParameters from JSP.

[Lucky J Verma]

Hi all
I have a display table in my jsp. In this table one column is clickable and clicking this sends 2 request parameters (ReasonsText and account)to my spring controller.
And i am creating links using Decoratros.
But there could be cases when first request paramter(reasonsText) can be extra large.It fails in that case .Is there any alternative to that?
I tried finding something in my database tables which i could use in place of reasonsText(like reason ID) but i use group by on reasonsText so i couldnot use id.

Please suggest.

<display:table uid="reports" style="font-size:12px" name="${reportList}"
			cellpadding="0" 
			cellspacing="0" 
			class="csTable"
			pagesize="10" requestURI="" decorator="com.pojo.myDecorator" >
				<display:setProperty name="css.tr.even" value="csZebra" />
				<display:setProperty name="css.tr.odd" value="" />		
				<display:setProperty name="basic.empty.showtable" value="true" />						
				<display:setProperty name="paging.banner.placement" value="bottom" />
				
				<display:column headerClass="TableHeader" title="Form" style="width:10px;" property="form" group="1"
			 />
				<display:column headerClass="TableHeader" title="Count" style="width:10px;" 
				property="count" total="true" />
				
				<display:column headerClass="TableHeader" title="Reasons" style="width:150px;" property="reasonsText" />
				<display:column headerClass="csFirst" title=""  style="width:50px;" property="details"  ></display:column> 
			</display:table>
			
			
			
			
			
public class MyDecorator extends TableDecorator {

	
	public String getDetails() {

		if (getCurrentRowObject() == null || !(getCurrentRowObject() instanceof ReportsPojo)) {
			return "";
		}
		MyPojo dto = (MyPojo) getCurrentRowObject();
		String decoratedColumn = "<a 
							+ dto.getReasonsText()
							+ \" rel="nofollow">"
							+ "Details" + "</a>";

		return decoratedColumn;

	}

}

Thanks

[Bear Bibeault]

Please be sure to ask Spring questions in the Spring forum. I have moved this post there for you.

[Mark Spritzler]

Remember that request URL with parameters have a length limitation. Typically it is better to have that submitted through a form, I would think. So that it ends up in the body of the request instead of as a request parameter. Or you can limit the amount of text the user can type in so that it doesn't reach the request parameter limitation.

Mark

[Lucky J Verma]

Hi Mark ,
Thanks for help.
Can you please give me an example on how to send data to @RequestBody for <display:table> column?
Adding it in form and then i use Will it automatically go to @RequestBody and not @RequestParam
. And data is sent in string.
Also i tried sneding POST data -by adding hidden fields to display:column and no which is not working .Since variables contain duplicated comma separated values
and no hint of what value was user-selected.
Furthur research taught me ts limitation of sending POST values.

[Ken Blair]

Lucky J Verma wrote:
Hi Mark ,
Thanks for help.
Can you please give me an example on how to send data to @RequestBody for <display:table> column?
Adding it in form and then i use Will it automatically go to @RequestBody and not @RequestParam
. And data is sent in string.
Also i tried sneding POST data -by adding hidden fields to display:column and no which is not working .Since variables contain duplicated comma separated values
and no hint of what value was user-selected.
Furthur research taught me ts limitation of sending POST values.

That's not what he's talking about.

A GET sends parameters in the request URL. A POST sends parameters in the body of the request. Because the length of a URL is restricted the length of the parameters is inherently limited. If you need to send a lot of data through a parameter, or even just a lot of parameters, you should prefer using POST as it's less likely to run into the length issues.

@RequestParam works for both. @RequestBody has nothing to do with it.

If you're getting a comma separated value it means that the parameter was included more than once. Look at your form and request URL and ensure you haven't submitted the value in two different places at the same time. If you're expecting multiple values for a parameter then it should probably be a List.