Hey
Ron Yust wrote:
> > Then again, with the above knowledge you can assume that if you do not
> > use clusters, and you never redeploy your bean, you should be fine using
> > statics :-) But then again, you might not want to *depend* on that if
> > you want to upscale your app later on. ;-)
> >
>
> But if the beans in one server are independent of the other clusters, then
> statics are fine, right? I don't assume that statics automatically mean
> someone is trying to communicate/share objects between jvm/servers. In a
> lot of cases, statics may simply be a way to communicate/share objects
> between CLASSES in a single jvm/server. Am I missing something here?
Iff beans in one server are independent on each other, and you don't
expect the static values to be "persistent" over time (re: redeployment)
you should be fine.
For example, the trick I mentioned re: user interface and security would
be a perfect candidate for statics in beans. In that example you
actually *want* the static information to be reset each time you
redeploy the application/bean.
/Rickard
--
Rickard �berg
@home: +46 13 177937
Email: [EMAIL PROTECTED]
Homepage: http://www-und.ida.liu.se/~ricob684
===========================================================================
To unsubscribe, send email to [EMAIL PROTECTED] and include in the body
of the message "signoff EJB-INTEREST". For general help, send email to
[EMAIL PROTECTED] and include in the body of the message "help".
