On 12/03/2004 21:26, Avinash Gangadharan [EMAIL PROTECTED] wrote:
People,
I have a design question. It is regarding the retrieval of parent and
child objects in the best possible manner. For eg. Let's say there is a
Person object with properties such as ssn, lastName and firstname. It also
People,
I have a design question. It is regarding the retrieval of parent and
child objects in the best possible manner. For eg. Let's say there is a
Person object with properties such as ssn, lastName and firstname. It also
has a list child objects ( Address ) of addresses and a list of
]'
Subject: [OT] Object Design Question
People,
I have a design question. It is regarding the retrieval of parent and
child objects in the best possible manner. For eg. Let's say there is a
Person object with properties such as ssn, lastName and firstname. It also
has a list child objects
Avinash:
...Adding to what Jacob says below: if you are writing your own, this is a good
link to study:
http://java.sun.com/blueprints/corej2eepatterns/Patterns/DataAccessObject.html
Regards,
Geeta
Hookom, Jacob wrote:
It's always on a case by case basis. When and how much do you need at a
, 2004 3:37 PM
To: Struts Users Mailing List
Subject: RE: [OT] Object Design Question
It's always on a case by case basis. When and how much do you need at a
given time? Hibernate/JDO/OJB/etc can handle these things for you via a
config to specify lazy relationships.
When you
together and then parsing them out would be better but sure not a clean
OO way of getting data.
-Original Message-
From: Robert Taylor [mailto:[EMAIL PROTECTED]
Sent: Friday, March 12, 2004 1:01 PM
To: Struts Users Mailing List
Subject: RE: [OT] Object Design Question
+1. Join
List'
Subject: RE: [OT] Object Design Question
That's the way I have it now, a view object querying the datastore and
forming the business objects. The view issues a query for the parent and
then calls the views of the children to give their list of objects for that
parent
7 matches
Mail list logo
