Hi,
>> So I believe the question is still open: how to run a scalable application
>correctly on WebLogic and Oracle.
Why does it matter that's it Weblogic and Oracle? I've been trying to follow this
thread and to me the only difference I see pointed out so far is that some app servers
have built in support for container optimistic locking by doing timestamp/version
check. If your app server doesn't support this out of the box then, like you said, get
something that does, like TopLink, or write it yourself. I don't think Websphere
(Advance Server) has built in support for container optimistic locking either, and if
I recall correctly in one of their Redbooks they talk about one approach to designing
a generic optimistic locking service as a stateless session bean available to all
entity beans. To say that your application is going to be incorrect and corrupt the
database if the your app server doesn't have built in optimistic locking is a little
hyperbolic in my opinion. I think part of the confusion (at least for me) is you guys
use the word transaction differently. One is talking about "business transactions"
that really span multiple "regular transactions." The database should be able to
handle concurrency for the later type of transactions. For the former that's the
developer's or app server's problem. Am I missing something?
Thanks.
--
Tinou
www.tinou.com
===========================================================================
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".
