What makes it not thread safe? If you are thinking in terms of s1, then
yes, but s2 actions are not reused and can therefore keep state as you
normally would have had to put in a s1 formbean.
On 11/30/06, Christopher Schultz <[EMAIL PROTECTED]> wrote:
-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1
Mark,
Mark Menard wrote:
> public String getDataRetrievedFromSessionBean () {
> return this.dataRetrievedFromSessionBean;
> }
Sorry for poking my nose in, but wouldn't this be horrendously
non-threadsafe?
Since I know virtually nothing about S2, I may be completely missing
something like action instances now live in the session or something
crazy like that.
Instead of using a method on the action, why not stuff the object into
the request?
request.setAttribute("dataRetrievedFromSessionBean",
this.getSessionBean());
Sorry if I don't know what I'm talking about.
- -chris
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.5 (MingW32)
Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org
iD8DBQFFb3sN9CaO5/Lv0PARAqmjAJ43fvmsWmR0VNEauKXZOjH8f+GORgCcCl/B
2HGBwx4xh0OCNwY8QRFmjaU=
=u3oN
-----END PGP SIGNATURE-----
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
--
James Mitchell
678.910.8017
