>I would like to know what approaches people are taking to design entity
>beans so that they behave in a read only manner and are sharable across
>users. I am really interested in a portable design not BEAs read only
>beans.
I think there is a lot of confusion in the industry about the meaning of
"portability". Portable software is software that doesn't need code changes
from system to system. If code needs reconfiguration of its associated
configuration files (or in the EJB case, Deployment Descriptors), then the
software is still portable.
Tom, I am pretty sure that many different application servers support
the concept of read only beans (Weblogic, Inprise, ...), but they require
proprietary entries in their XML descriptors. Thus I would recommend
keeping your entity bean-based read-only design, it is portable indeed.
Floyd Marinescu
---------------------------------
Senior Architect / Director of Marketing
The Middleware Company
http://www.middleware-company.com
http://www.TheServerSide.com
[EMAIL PROTECTED]
416-889-6115
Check out TheServerSide.com, the internets first J2EE community!!!
===========================================================================
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".
