Skip to main content

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index] [List Home]
RE: [cosmos-dev] CBE persistence work

Hubert,
 
Are the extensions that TPTP needs too complicated to hide in a "user extension" column? 
 
It doesn't seem unreasonable to me that a generic CBE database might include a user-defined field that is associated with each event.  If not, we probably need to define a "non-EMF TPTP CBE model" that is an extension of the generic one.  If we design the APIs well, a non-TPTP consumer would request a generic CBE return type which could be returned from either type of database.  This consumer would be shielded from any extensions that he didn't specifically request (and wouldn't understand) while TPTP could request its own type.
 
BTW, I suspect that you meant for the oval to the right of the model converter to be labeled "non-EMF CBE model".
 
Regards,
 
Don


From: cosmos-dev-bounces@xxxxxxxxxxx [mailto:cosmos-dev-bounces@xxxxxxxxxxx] On Behalf Of Hubert H Leung
Sent: Wednesday, May 30, 2007 3:42 PM
To: cosmos-dev@xxxxxxxxxxx
Subject: [cosmos-dev] CBE persistence work


Here is the wiki page that document my work on writing and reading CBE to RDB using iBatis and the problems encountered:  http://wiki.eclipse.org/index.php/COSMOS_CBE_RDB


_________________________
Hubert Leung
IBM Toronto Lab
hkyleung@xxxxxxxxxx
905-413-3382

The contents of this e-mail are intended for the named addressee only. It contains information that may be confidential. Unless you are the named addressee or an authorized designee, you may not copy or use it, or disclose it to anyone else. If you received it in error please notify us immediately and then destroy it.

Back to the top