One option might be a static HashTable in some class... key the table by
some calculated ID representing the request.. for that, see the
RequestHelpers.generateGUID() method in Java Web Parts:
http://javawebparts.sourceforge.net/javadocs/javawebparts/request/RequestHelpers.html
(http://javawebparts.sourceforge.net)
Then, store your bean under that key. Then, you can retrieve it in your
JSP.
Problems with this:
* Using a synchronized collection will obviously have performance
implications. Synchronization isn't the killer it used to be, so you
may find it's not much of a problem, but you'll definitely want to be
careful
* Take care to remove the item from the collection at the end of your
JSP, otherwise you'll run out of memory at some point since it'll just
keep growing with each request. Maybe no boom today. Boom tomorrow,
there's always boom tomorrow
(http://www.ao.com/~regan/quotes/Science_Fiction.html).
Frank
Scott Van Wart wrote:
Sonu S wrote:
I can not store bean in request or session or any scope (design
issues...)
If you can't store the bean in any scope, then you really have no way of
getting anything from the action to the jsp... I see no solution to your
problem with this constraint.
- Scott
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
--
Frank W. Zammetti
Founder and Chief Software Architect
Omnytex Technologies
http://www.omnytex.com
AIM: fzammetti
Yahoo: fzammetti
MSN: [EMAIL PROTECTED]
Java Web Parts -
http://javawebparts.sourceforge.net
Supplying the wheel, so you don't have to reinvent it!
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
