Win a copy of Kotlin in Action this week in the Kotlin forum!
  • Post Reply Bookmark Topic Watch Topic
  • New Topic

Any other alternative?  RSS feed

 
Mallika Kumar
Ranch Hand
Posts: 61
  • Mark post as helpful
  • send pies
  • Quote
  • Report post to moderator
Hi,
I'm creating a query tool, through which users can enter values and look at multi-page results. The way I'm doing it is this:
I have an ejb(stateless session) which performs the query, gets the results, and puts the result in an object(lets call it a result object). From this result object, we get a vector containing all the rows. I have a java bean class which acts as a layer between the ejb, and jsp pages(which are used for presentation.)
Now, I have a page scoped bean of the intermediate java bean class, which gets performs the query, in my jsp page. I have another session scoped bean in the same jsp page, which takes the vector and displays all rows page-by-page.
All these are working fine. But I'm apprehensive about the vector being in the session scoped bean in my jsp page. In other words, I'm adding the vector object to the session(using the session scoped java bean), and displaying rows from it spanning many pages. Supposing my query gets 500 rows, using this technique seems bad.
What other technique can I use to prevent having the vector in the session ? I cannot pass resultsets into the jsp page, as I'm cloging all connection and resultset objects in the ejb itself. This is not an alternative................
Any response will be helpful.
Thanks.
 
Peter den Haan
author
Ranch Hand
Posts: 3252
  • Mark post as helpful
  • send pies
  • Quote
  • Report post to moderator
Please check out the very similar question here.
- Peter
 
  • Post Reply Bookmark Topic Watch Topic
  • New Topic
Boost this thread!