Hi Roland, OJB hides the underlying data model and JDBC detail, so ideally changes in the data model would have minimal impact on your application. If you feel that your application might get too coupled with OJB, perhaps you can create another layer of abstraction between them. This also allows you to switch to another O/R mapper easily (again, under ideal situation). ;-)
Regards, Lee Haw -----Original Message----- From: Roland Carlsson [mailto:roland.c@;swetravel.se] Sent: Tuesday, October 22, 2002 4:41 PM To: OJB Users List Subject: Designing application Hi! I didn't find this in the documentation on the homepage. How should one design an application that uses OJB? The PersistensManager shall hide the database for the programmer. But should the rest of the application be dependant on OJB-classes? To me this feels almost as bad as writing directly to the database. Is there any examples of how to handle this? What designpatterns apply for this? Is this a problem or am I thinking to much instead of programming? Regards Roland Carlsson -- To unsubscribe, e-mail: <mailto:ojb-user-unsubscribe@;jakarta.apache.org> For additional commands, e-mail: <mailto:ojb-user-help@;jakarta.apache.org> -- To unsubscribe, e-mail: <mailto:ojb-user-unsubscribe@;jakarta.apache.org> For additional commands, e-mail: <mailto:ojb-user-help@;jakarta.apache.org>
