Hi Cedric, Jonathan & Evan,
Having used both BEA's WebLogic & the Borland AppServer
(as well as a few others but not the sybase EAserver
yet) in production environments, (non-trivial projects I
might add), the "exclusive" mode is hardly ever used even
when the database is _not_ shared.
However if an underlying row in the database has been
removed (as jonathan mentions - unbeknownst to the
container), and I call a business method on an entity bean
reference - which (arguably) does not cause any
getters/setters to be executed - then as a user(client),
I would still expect an exception.
why? simply because the reference now points to a
non-existent object.
I'm not taking sides here ... just throwing in a view as to
what a user perceives/expects would happen in the above
case. And if the ejb 2.0 (& 1.1) specs are not definitive
on the above behaviour, I would logically expect the above
to happen i.e. an exception being thrown.
Maybe other users will (dis)agree?
-krish
>
> I'll let the readers decide for themselves. I don't know about you guys,
> but this discussion has made me thirsty.
>
> --
> Cedric
===========================================================================
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".
