Mike wrote:
> We ran into similar design problems with making essentially 'static' data
> available to lots of clients (in our case servlets). EJB entity
> beans just
> don't seem suited to this type of access (witness the long list
> of notes on
> this topic recently). The spirit of EB are persistent domain object
> instances that are transparently managed by whatever EJB container you
> choose to purchase.
As the initiator of this thread, I have come to the conclusion that the only
way to solve this real world problem is to go outside the EJB framework
(e.g. RMI/CORBA etc..). It is apparent that EJBs set out to address a
narrower range of applications. I am concerned that because all the tool
vendors are focusing purely on EJBs now, other frameworks may not get enough
attention from them. I would vote for broadening the scope of EJBs to
address this type of application also, so we can have vendor neutral
implementations.
Comments from Javasoft?
Jawahar
===========================================================================
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".
