I would like to present my experience designing with entity/session
EJB. Our application is targeted towards the Telecommunications
industry. More precisely, this application is a Network Management
System to configure and manage a network of ATM (Asynchronous Transfer
Mode) switches.
Based on our analysis of our problem domain (ATM switches) we designed
an object data model which presents a structural view of our data.
Objects in this structural object model have 1-to-many,
many-to-many associations and aggregation relationships. Our
data objects map to entity EJBs. Since we are using Oracle as the
underlying database, and WebLogic as the container, we have decided
on using TOPLink for WebLogic to do the OO-RD mapping. TOPLink
is very easy to use, and it maps/manages complex relationships
(many-to-many, 1-to-many). The relational database model will follow
the object data model closely, except in cases where to get from point
A to point X involves traversing many objects, we may have
a join table between A and X. This join table would increase
performance when doing A-X join selects.
We are currently starting to design the behaviour object model which
will operate on the entities (object data model, described above).
Our behaviour object model will consist of objects which will map to
statefull/stateless session EJBs.
My $0.02.
Rubens.
===========================================================================
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".
