----- Original Message ----- From: "Rickard �berg" <[EMAIL PROTECTED]> > The conclusion is that it is impossible to use > * optimistic concurrency control in the container > container and > * caching of Entity data and > * SERIALIZABLE isolation level in the DB What serious, enterprise application can rely on the caching of entity data? Of course there are some specialized apps (i guess) that truly *own* their data and can use Option A, but for most *real world* apps, this is a pipe dream. Even in a new application that does not share it's data now, you can't predict what the future requirements for that data may be. jim =========================================================================== 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".
- Re: optimistic locking and deadlock (was EBs are slow) Lahooti, Hamid
- Re: optimistic locking and deadlock (was EBs are slo... Victor Langelo
- Re: optimistic locking and deadlock (was EBs are slo... Thomas Alex
- Re: optimistic locking and deadlock (was EBs are slo... Lahooti, Hamid
- Re: optimistic locking and deadlock (was EBs are slo... Rickard �berg
- Re: optimistic locking and deadlock (was EBs are slo... Lahooti, Hamid
- Re: optimistic locking and deadlock (was EBs are slo... Rickard �berg
- Re: optimistic locking and deadlock (was EBs are slo... Lahooti, Hamid
- Re: optimistic locking and deadlock (was EBs are slo... Rickard �berg
- Re: optimistic locking and deadlock (was EBs are slo... Rickard �berg
- Re: optimistic locking and deadlock (was EBs are slo... Rickard �berg
- Re: optimistic locking and deadlock (was EBs are... James Cook
- Re: optimistic locking and deadlock (was EBs... J. Matthew Pryor
- Re: optimistic locking and deadlock (was... James Cook
