Though this is more of a design question I wanted the reccomedation. I can design persistent class in 2 ways:

1. Have private attributes similar to the Java bean convention
2. Have a HashMap and write suitable getter and setter methods that put or get from the map.

The advantage that I see is as follows:
1. Development time - Would be relatively less
2. If I add new columns I would just add new getters and setters with keys.

Which is a reccomended approach.

Thanks,

anand

1 is the way to go, 2 is really strange because you loose type safety and evertyhing.

Thanks. For Persistent object I guess following JavaBean conventions is the best approach.

However say I have DTOs then would it make sense to have the 2nd approach. I could have a super class that would centralize access and provide method to cast the values into their respective types.

I guess it's a trade off between time taken and complexity that would decide it.

-Anand