I'm trying to put together a talk/white paper on "problems with EJB
architecture in data-centric business applications, and what to do about
them." Do you have any candidates? Or pointers to relevant information? Or
comments, expansions on my starter list?
If anything useful comes of the exercise, I'll write it up and post the
results.
CANDIDATE GRIPES:
Overall:
No persistant operation interceptors (for computed values in CMP)
No event model to support shared cache (client side, or split between
servers)
No server-only invocation (always need a client)
No client-side data caching support
No optional features/extension mechanism
Single-thread architecture
Entity Bean Problems
No portable BMP
No plug-in CMP (so CMP isn't portable between EJB Containers)
No container-managed association/relation
No bulk operations support (stored procedures, or operations at level of
entire table)
Session Bean Problems:
No portable persistent state description
Single-client restriction
No sharable-state for multiple SB in the same Session
----
This list is cross-posted to two mail lists. To unsubscribe,
follow the instructions below for the list you subscribed to.
For objectweb.org: send email to [EMAIL PROTECTED] and
include in the body of the message "unsubscribe ejb-container-group".
For enhydra.org: send email to [EMAIL PROTECTED] and include
in the body of the message "unsubscribe ejb-container-group".
