I wrote a post on this some time back, but alas didn't get any
responses.
I think having an in-memory implementation of EJB-QL could provide a
huge optimisation to JBoss and would also make it possible to use
non-JDBC datastores.
As Peter notes, it wouldn't make sense for all entities, but of th
Luttrell, Peter wrote:
> My app runs on a slow database. To compensate i have a
> longer-then-normal bean-cache lifetime and use commit option A - thus
> once they are loaded, they are always in cache.
>
> This works great except for finder methods, because they hit the
> database to select i
My app runs on a slow database.
To compensate i have a longer-then-normal bean-cache lifetime and use
commit option A - thus
once they are loaded, they are always in cache.
This works great except for
finder methods, because they hit the database to select ids based on query
parameters.
