Originally posted by Merrill Higginson:
As I see it, you have 3 main viable choices:
put a property for the query in your form bean, and in each jsp, put a hidden field for the query on the page. This will pass the query from page to page without it appearing as part of the URI. Put it in the HTTPSession. If it's just one string, I don't see it as a big scalability issue to store it in the session, even for thousands of users. Obviously, if you're doing horizontal scaling, your app server will have to have a means of preserving the session across multiple instances of the app server. Store it in a cookie on the browser.
Originally posted by kanishtha Kramalekhakha:
If your need is to show result set as it is in your JSP you can use some reporting tool. But because of you needs to have checkbox in your page your page is going to be a form. (You are going to fetch user inputs). So you have to handle pagination by yourself. I could be wrong (sometimes). Please keep me informed if you found some easy way of doing that.
Originally posted by Craig Jackson:
I hope I understand you question correctly, but can't you enlose your search parameters(i.e. drop down list(s), text boxe(s)) in a form document and set the method attribute to "POST". This will store your search parameters inside the request object instead of request parameters of your url.
Originally posted by Ken Loh:
Does JOIN work in EJB-QL ? You may want to UNION results with country <> null and those with results=NULL.
Originally posted by Sarath Mohan:
How this code will complie?
The above code never satisfies, since session is not a boolean value but an object.
Compare with null and do the logic
Originally posted by Damanjit Kaur:
Ya, but thats a very weird solution. Hope somebody else having solution, reads this thread and provides it.