can anyone make any suggestions as to the best way to design a persistence
interface so that one may switch among castor, ejb, ojb, jdo, etc.?
basically, i will have session beans accessing/manipulating data objects.
because of the various persistence mechanisms currently available and
uncertainly of their futures, i would like to design my system to
access/manipulate data via a persistence interface, rather than writing
directly to a particular persistence mechanism. initially, i'm focusing on
castor (as i really like its concept and hope to be able to use it well
into the future), but may need to switch to ejb or other mechanism at a
later date, so would like to put a layer between my business logic (session
beans) and the persistence mechanism.
is anyone currently doing this? can anyone make recommendation as to how
one should implement such a persistence interface?
my apologies if this is off-topic...
-----------------------------------------------------------
If you wish to unsubscribe from this mailing, send mail to
[EMAIL PROTECTED] with a subject of:
unsubscribe castor-dev
