> so, what many people say, that this has limitations in scalability
> (probably won't be able to build amazon.com that way) is true but it's
> oversimplifying to say there are no areas where this approach is good in
> real world practice or that those areas are not ejb-typical. ejb != 1000
> transactions per second type of applications.
So, i guess a conclution would be to use sql wrapped in session beans when
the transaction load is greater than 1000 (which is quite a huge load :-)
Generally i don't like the thought of building on a technology that i would
need to hack around and directly access the database again, by-passing the
ejblevel. Hopefully that is NOT the case in 99% of the cases.
/Jon
--
--------------------------------------------------------------
To subscribe: [EMAIL PROTECTED]
To unsubscribe: [EMAIL PROTECTED]
Problems?: [EMAIL PROTECTED]
