Check out the FAQ on the OJB site, I think theres some advice about app design(in the last question/answer if memory serves).
Eliot On Tue, 22 Oct 2002 10:41:19 +0200 "Roland Carlsson" <[EMAIL PROTECTED]> 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. > > 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>
