Win a copy of The Little Book of Impediments (e-book only) this week in the Agile and Other Processes forum!
  • Post Reply
  • Bookmark Topic Watch Topic
  • New Topic

response.setRenderParameter is full?

 
Susan Mincey
Greenhorn
Posts: 13
  • Mark post as helpful
  • send pies
  • Quote
  • Report post to moderator
In my ProcessAction, I am returning a StringBuffer from a method and converting it to a String and then setting it with response.setRenderParameter("param", String) so that I can access it in my doView. However, it seems that the response "bucket" cannot accept all the data in my String.

If I remove some of the data and pass it into the response.setRenderParameter, I have success. So I got creative and divided the data into 2 StringBuffers(sbA sbB), converted each to a string (strA strB) and set them as 2 different RenderParameters ... that did not work either. The error I get in both cases is a blank screen - the page and the 2 portlets on that page do not render.

Is there a limit to the size of the string I can set into the response.setRenderParameter?
 
Susan Mincey
Greenhorn
Posts: 13
  • Mark post as helpful
  • send pies
  • Quote
  • Report post to moderator
I solved this myself but would still like to hear from anyone with knowledge about limitations for the renderParameter.

I solved this by moving everything to the doView method. So know my processAction receives the action, gets the record ID number and sets that in the renderParameter. The doView now gets the record ID and creates an object by calling the DB query method, take my object and pass that to the buildForm method and then do a print using the string I created in this method. This works great.

I am curious as to whether this is the correct architecture or not as I am trying to build JSR-168 according to the recommended architecture.

Thanks in advance for providing any guidance or suggestions.
 
  • Post Reply
  • Bookmark Topic Watch Topic
  • New Topic