When using EJB within a relational world,
I've found that there are at least 2 Layers of mapping.
1) Entity Bean TO relational database
2) Non-persistent classes TO Entity Bean
NOTE: the non-persistent classes may be a request sent
to a Session bean. The session bean breaks up the
request
and maps it in some fashion to an entity bean for
lookup/update.
The Mapping tools which I have encountered only deal with the
Object to Relational mapping. There doesn't seem to be an Object to Object
mapping. The Object to Object mapping is currently handled manually
(hard coded) for our project.
All of this mapping doesn't seem to be buying us much in terms of
flexibility.
If the database changes, we now have to change two mappings.
Is there a better way?
TIA,
Steven Lee
===========================================================================
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".
