Looking for a better design: how to populate db result to object with lists

Question

I have a query that returns from the db an arrayList of class CarBean:
carID, model, color, rentUserID, fname, lname, dateRentStart, dateRentEndThe query is with reference to a particular car that N people (rentUserID) rented and the user (the system user) wish to know how many rentals were made for this carID.
I wish to populate the result into ONE class name CarRental which looks like this:
private Car; //model
private List<RentUser> rentals; //all info relating to rentUserso, my question is this, what creative way (Design Pattern, maybe?) is there to populate all the objects (CarBean) from the arrayList into CarRental?
In my solution I'm doing something like this:
Iterator<CarBean> itr = list.iterator();
CarRental carRental = new CarRental();
List rentals = new ArrayList();
while (itr.hasNext())
    CarBean cb = itr.next();
    carRental.setCarID(cb.getCarID);
    //for the list of users:
   User u = new User(); 
   u.setUserID(cb.getUserID()); 
   rentals.add(u);
carRental.setRentals(rentals);* please consider a more complicated query that the end result of ONE object should have X arrayList and other M objects in it
thank you!

Answer 1

Just to make sure I understand, here's a simple version of your question. Please correct anything I have wrong.
Your design will have two classes: Car and Renter. A Renter is a Person who rents a Car on a given day:
package model;
public class Renter implements Serializable
    private Long id;
    private String name;
    private Address address;
    // Details left for you.
}You'll also have a Car:
package model;
public class Car implements Serializable
    private Long id;
    private String make;
    private String model;
    private int year;
    // Details left for you.
}It sounds like you want to have a one-to-many relationship between Car and Renter. I think you have a couple of choices:
You can embed a List<Renter> as a data member inside the Car class, or
You can encapsulate the relationship between a Car and a Renter in a separate class like a Contract.
I kinda like the second option because it reifies a nice concept.
As far as the database goes, I'd recommend following an idiom from Spring- their RowMapper interface:
package persistence;
public interface RowMapper
    Object map(ResultSet rs);
}Encapsulate the mapping from ResultSets to Objects that way.
Or use Hibernate, TopLink, or another ORM tool.
%