Julian13
发贴: 387
积分: 52
|
于 2003-06-19 09:09
agree with floater that data object should be abstracted from your persistence mechanism. this make you flexible to adopt different way to do the persistence job, either entity bean, hibernate or even jdbc directly. for these implementation, i guess the xdoclet may help your fasten the job by utilizing its tag for entity bean or hibernate. thus, you can minimize the tedious coding work of course, coding by hand let you consider more about the persistence design.
floater also bring out point that business logic should be decouple from technnology (or the ejb container as he stated). for these implementation, i think we can make those business operation remain inside your domain model classes or some business classes and wrapping them by a session bean for its ACID. such that you can wrapped those operation by different transaction mechanism later. for me, i used to wrapper those operation with a jdbc connection since my project scope need not using j2ee container
about the UI, as long as the MVC pattern being enforced. it should capable to deal with web frontend, swing GUI or even text mode console. of course, the value-object pattern will play an important role for different nature of UI implementation.
|