Imre,
I agree with Ed. The problems applies to most distributed computing models. I
use entity beans or similar to provide re-useability (through fine grained
access methods) and session beans for performance optimization (through process
oriented APIs: one clieck = one remote invocation). I got a nice picture for
this but I'm afraid mime mails don't make through the list server.
Imre Kifor wrote:
> Here is why I very strongly oppose this unrestrained session bean wrapping
> idea. Any call on a session object can throw an "object expired" exception
> (remember the session timeout?). This means that in the client *every* call
> (to session objects) has to be protected and at *any* level you have to
> support the recreation of the session objects. If this is not an artificial
> complication of the client code then I don't know what is.
The activation/passivation for session beans comes in handy here. You just
de-activate a session instead of expire it.
Cheers,
Andreas
--
"Programming with Enterprise JavaBeans, JTS and OTS" is now available. Collect
all three!
www.wiley.com/compbooks/vogel
===========================================================================
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".
