I am given a task to design a standalone (desktop based) client program. It basically retrieve tabular data from server, like show show all the customer info in a month.

There will be a list column view (tabular form), showing data based on the criteria: age, gender etc.

It looks to me like a table viewer for database. Should I use hibernate for this? I don't see any domain model in the design.


Thanks :)

I wouldn't use Hibernate for this sort of application.

Hibernate can be very useful when you have a domain model, but your scenario looks more like it would be more suited for a table module (see Fowler Pattern's of Enterprise Application Architecture) approach.

Just my 2 cents.


--
Stephen Souness

Thanks Sounie!

Another question:
1. If you were to use Table Module pattern, will you still using Hibernate? I am asking this because Hibernate can run manual SQL function.

Thanks again. :)

Hi,

If you're going to be writing the queries as straight SQL, what will Hibernate offer over direct JDBC?

Maybe some query caching?

Anything else?

--
Stephen Souness

hmmm... perhaps I don't have to create/close connection with try/catch clause in every class? or perhaps it is more portable? I don't know. This is the first time I use it.

If you want something else to take care of establishing connection and ensuring resources are closed on exceptions, then there are other options.

For example, Spring provides a JDBCTemplate, see:
http://static.springsource.org/spring/docs/2.5.x/reference/jdbc.html

--
Stephen Souness