Hi Robert
What I try to do is create aggregation of objects with value objects and
entities and create repositories that would give me all information
related to specific relationships. am sorry if it sounds vague, but u
might take a look at Domain Driven Design for your domain model.
hth
Patria
Robert Campbell wrote:
Hey guys,
Over the years I've been constantly annoyed by a recurring issue I
face: domain objects that start simple (ex: User) mapped to a
similarly simple table (ex: users, roles, etc). As feature creep sets
in, the User grows bigger and more complex. The perfect example is
this:
Event (like a conference). Then I have to add a set of hotel
accommodations, so I break that off into its own domain object, attach
it as a member attribute of Event. Sponsors are added, files, dates,
alerts, a million things. All of these I try to break off into small
pieces and attach to Event. Over time, however, the Event object
becomes a mass of member attribute lists, objects, etc. Then, to load
one Event, you have to load from a million tables, so I do lazy
loading.
Anyway the point I'm trying to make is that I'm sure this type of
problem is faced by many people. Does anyone know of any guides/design
patterns/best practices for dealing with this?
Thanks!
Rob
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
--
Patria H.Lukman (Mr.) | Sun Certified Professional
Luk-Zen Technologies Inc | "Being Agile with Java" | www.lukzen.com
Cell: (+) 1.514.705.5593 | Fax: (+) 1.514.227.5201
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
