David, I think Unit or Work pattern tries to solve some other problem rather than decoupling the Business Objects from the database as asked earlier. Although it can be employed to perform the function.
I think having a simple interface for the database related functionality in the app will solve the problem. We can always change the database/database classes (e.g OJB classes) behind the interface and the BO's will not be affeected by it. Affan ----- Original Message ----- From: "David Leal" <[EMAIL PROTECTED]> To: "OJB Users List" <[EMAIL PROTECTED]> Sent: Tuesday, October 22, 2002 2:28 AM Subject: Re: Designing application > Roland Carlsson wrote: > > > 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. > > > Hi Roland, > > Try the Unit of Work pattern (see http://martinfowler.com/isa/unitOfWork.html). > > > -- > 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>
