what makes an Value object?

Thread view:

Elhanan - 07 Nov 2006 14:15 GMT

hi..

i have an entity class (which is a many to many class) which has
several fields which to me could be in a different object linked by a
one getter and setter.

this class is called RequestPlan and has one person and one policy

it also have InsuranceCode,Insurance Type and several others fields,
which could be in a differnet class as a value object becouse they
represent the product itself, essetially this class wil contain data
about the products and how they are used under the context of the
current policy and person.

what do you think?

Reply to this Message

Daniel Pitts - 07 Nov 2006 19:38 GMT

> hi..
>
[quoted text clipped - 11 lines]
>
> what do you think?

If it simplifies your code, and satisfies your requirements, I say go
for it.

By simplify, I mean makes it easier to understand. Keep in mind that
you can always refactor if your current design ends up not being good
enough.

Reply to this Message

Elhanan - 08 Nov 2006 06:55 GMT

the entire model may simplfy my code, however it does not simply the
process with fills it with data from legacy code.
my model should be saved in a database with hibernate, with many to
many relations, and since the erd does allow duplicate records i won't
allow duplicate instances of entities in my model.

> > hi..
> >
[quoted text clipped - 18 lines]
> you can always refactor if your current design ends up not being good
> enough.

Reply to this Message

what makes an Value object?

Free Magazines