I have just completed the development of our ATM-NMS
(Asynchronous Transfer mode Network Management System)
object data model which consists of 15 BMP entity beans. The
entity beans map to tables, and relationships between
the beans have been provided in the remote interface when
necessary.
I am not in favor of using CMP, because it basically makes
your code non-portable, and does not provide all the
flexibility BMP provides. It is my experience that
containers provide caching for entity beans, therefore having
a second level of cache (TOPLink, for instance) is not
going to buy much. Besides, writing JDBC/SQL calls is
the simplist thing in the world. Updating the schema is
also no big deal, because the tables are centralized on their
own beans, which makes a central point of change.
I will be glad to elaborate other reasons, for instance,
- time to learn TOPLink vs. JDBC/SQL
- extra cost involved in getting a third-party product.
--
Rubens S. Gomes, NMS Software Development Engineer
Fujitsu Network Communications, Inc.
Raleigh, NC, 27609 USA
XEmacs -- Emacs: The Next Generation
===========================================================================
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".
