| Ron Yust wrote:
|
| > Wow! No static methods/data, no file i/o, no threads, no sockets, no
native
| > code. Sounds like EJB is an unruly teenager about to take the family
car
| > out on a date. Geeesh, just neuter the EJB application! I may end up
| > sticking with my trusty old RMI server.
|
| Sounds pretty bleak, doesn't it? I think it shows the relative
| immaturity of the EJB/J2EE architecture.
hi!
Regarding the singleton issue, I think there should be a hybrid EJBean
type: something that can be shared like an entity even between different
JVMs, stays alive after passivations like a stateful session bean (or
possibly
make it stay in memory as long as xxx specific method is not called, also
we may achive performance since it's always in-memory).
We may call it SingletonBean!!
I think it shouldn't be that hard to implement it...
Ara Abrahamian
bi!
===========================================================================
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".
