It seems to me that the lack of a specification for read-only entities is a major hole in the EJB spec. Does anyone else agree?
I'm referring to the "lock-upgrade" problem: in plain vanilla EJB, every access of an entity bean results in an ejbLoad() and an ejbStore(): meaning even read-only operations result in a database write, and thus a need for an exclusive (writer's) lock. So concurrent reads are essentially serialized.
Of course, every serious app server has read-only semantics built in one way or the other. But that's exactly the point: it's one way or the other. Why don't we have a standard for this?
I'm totally flabbergasted that EJB 2.1 *still* doesn't include this. What do you think?
Kenneth DeLong
Senior Consultant
Direct: 510-517-5839 (Cell)
Fax: 972.789.1340
Valtech Technologies, Inc.
5080 Spectrum Drive
Suite 1010 West
Addison, Texas 75001
www.valtech.com <http://www.valtech.com>
transforming technology skills
into sustainable business value
