> - Replace entitity beans with stateless beans (+ DAO
> and readonly
> cache) for real live objects exposed to intensive concurent
> access (like
> a StockBean that is currently accessed by thousand of speculators).
> - Replace entity beans by stateless beans for
> "objects" that are less
> interactive and often subject of mass update.
Could you elaborate on your update mechanism for this read-only cache
mentioned in a earlier post? Since you use StockBean as an example, which is
quit often updated....
And also, I'm into the same design problem where I have a lot of read-only
data which are updated trough some other server side process.
I'm thinking on doing something like this:
JSP -> JavaBean -> StatefullSession (converting data to XML) ->
StatelessSession -> Database
Where the StatelessSession beans doing the actual calls to the database, by
using DAO. Any comments?
The JavaBean are doing the XML-XSL processing. Comments on this also
appreciated....
Anybody having a good pattern/design for managing the db-connection in the
SSB and the SQL strings in the DAO?
/kjetilhp
===========================================================================
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".
