When I read things like this, I wonder if EJB will really survive long term.
Seems if everyone has to program for the common denominator to achieve the
holy grail of portability (EJB's big selling point), you can't take full
advantage of everything EJB purports to offer.
Am I the only one who wonders if the emperor has no clothing?
>
> According to the WebSphere doc, Option A is supported but only if you are
> not running clones (clusters) of the application. In the configuration for
> individual beans, you can set "Database access" to "exclusive" to get Option
> A behaviour, or set it to "shared" for Option C behaviour. Again, because
> the cache is not shared across JVMs or machine nodes, you can't use the
> "exclusive" setting unless you are running your application on a single JVM.
>
===========================================================================
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".
