Hi Matthias! Thank you a lot for your reply! $kala. ----- Original Message ----- From: <[EMAIL PROTECTED]> To: <[EMAIL PROTECTED]> Sent: Thursday, October 24, 2002 1:00 PM Subject: AW: Designing application
Hi Marian, sorry about the delay of the answer, but I am not every time in the office. And there are so much EMails from OJB. Here are some Picturs about the design. I hope it is help full for you. Best regards Matthias -----Ursprüngliche Nachricht----- Von: Marian Skalsky [mailto:ms@;euromove.sk] Gesendet am: Mittwoch, 23. Oktober 2002 09:25 An: OJB Users List Betreff: Re: Designing application Hi Matthias! I would like to ask you to create some example, best would be to draw some picture with notes, about the approach you mentioned (using of Facada and Delegate pattern) when designing the app. It would be nice to see the structure of this part of the app (class diagram) and how the interaction works on some example business object. I would like to try this approach, but it is not completely clear to me. Would you be so nice :)? Thank you. $kala. ----- Original Message ----- From: <[EMAIL PROTECTED]> To: <[EMAIL PROTECTED]> Sent: Tuesday, October 22, 2002 12:03 PM Subject: AW: Designing application Matthias, for chage in the futere the O/R mapper I use the Facade-Pattern. To hide some technical things to get the Facade, I use the Delegate-Pattern. So the BO's are full decoupled from the DB-Layer. Matthias -----Ursprüngliche Nachricht----- Von: Affan Qureshi [mailto:quereshi@;etilize.com] Gesendet am: Dienstag, 22. Oktober 2002 11:49 An: OJB Users List Betreff: Re: Designing application 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> -- 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> ---------------------------------------------------------------------------- ---- > -- > 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>
