Report design issue for discussion

Question

I'm going to generete several reports using JSP--session EJB,session bean
retrieve database,return result to JSP and show in browser.
I like resultset,but resultset is not Serializable, so can't send one across
the wire.
if I turn the ResultSet into a Vector,send vector to JSP,I'll have to build
diffrent structure classes for each reports.I like the resultset becuse it
seems "consolidate" for diffrent tables
JDBC2.0 provides cachedrowset,but it seems only good for small set of
data,for report,I need to return alot of data
do you have any sugguestions

Answer 1

Suggestion:
Unless you have a good reason, don't use EJB for this.
1) It is non-transactional (probably)
2) It is not distributed (ejbs are probably local)
3) Were it distributed, it would suck (high cost of transmission with
report-scale data)
4) You are fighting something ... if it doesn't seem natural, it probably
aint.
Peace,
Cameron Purdy
Tangosol Inc.
<< Tangosol Server: How Weblogic applications are customized >>
<< Download now from http://www.tangosol.com/download.jsp >>
"John Zhang" <[email protected]> wrote in message
news:3c080711$[email protected]..
I'm going to generete several reports using JSP--session EJB,session bean
retrieve database,return result to JSP and show in browser.
I like resultset,but resultset is not Serializable, so can't send oneacross
the wire.
if I turn the ResultSet into a Vector,send vector to JSP,I'll have tobuild
diffrent structure classes for each reports.I like the resultset becuse it
seems "consolidate" for diffrent tables
JDBC2.0 provides cachedrowset,but it seems only good for small set of
data,for report,I need to return alot of data
do you have any sugguestions