George - thanks (BTW with Ron you seem to be the person I know of the most mailing lists - we need to get you some more work :-)
I think I touched on your wrapper approach in my previous email. Like you I have used it in the past as an approach but it requires additional discipline from the dev team. Scrum already tries their discipline and I wish to conserve its use :-)
On Sat, Apr 12, 2014 at 1:38 PM, George Dinwiddie <lists@...> wrote:
?
Mark,
On 4/11/14, 1:50 PM, Mark Levison wrote:
>
>
> I'm running an Agile Development course with some wonderful people at a
> client who're addicted to their existing ORM. We've been discussing the
> evil involved in Data Classes (i.e. classes with no behaviour). In their
> world the habit of creating data classes comes from the fact that their
> ORM (Hibernate and JPA) creates POJO type objects and they manipulate
> them. They get the problem but would live to see an example of project
> that doesn't do this.
>
> Do you know an OpenSource project that doesn't a use POJOs to get its
> data in/out of an RDBMS? Do you know an ORM that helps people avoid
> creating Data Classes?
I don't have any examples to show, but a pattern I've used successfully
is to encapsulate the "data object" within a business domain object.
Typically I've used the data object as a parameter to the domain object
consctructor, and provided a getter for when (if) I needed to recover
the primitive for some reason. Often the user (ORM in this case) doesn't
actually need a data-only object, anyway. It just needs some
bean-pattern getters and setters for the fields it's to understand.
- George
--
----------------------------------------------------------
* George Dinwiddie *
Software Development
Consultant and Coach
----------------------------------------------------------