No you are definitely right, having a few automatically mapped beans
is much better, one reasony why I use hibernate, but mapping objects
add an additional coding effort to the mix which cannot be underestimated...
Although mapping objects in my opinion are the cleanest way to bypass
the hibernate session problem, but they should not be needed...
Werner
Joshua Davis wrote:
-----Original Message-----
From: news [mailto:[EMAIL PROTECTED] On Behalf Of Werner Punz
Sent: Thursday, September 01, 2005 4:29 AM
To: [email protected]
Subject: Re: JSF + Spring + Hibernate
The point is (if I understand the Transfer Object stuff correctly)
that transfer objects arent a good solution.
In my opinion no, because once things get more complicated
(some relational stuff etc...) you run into myriads of
problems which you have to handcode, which you probably could
avoid if you just use the pojos from the db....
Doing a transfer object means, either flat out the data, or
also transfer the relational data into other transfer objects...
you end up basically with twice the work, and not really a
timesaving to plain jdbc... access or a rather simple direct
table to object mapper.
Maybe it's just my opinion, but I'd rather make a few simple java beans than
deal with lots of JDBC code that is completely locked in to a particular DB
vendor. But... To each his own. Use what works for you. :)
Heck, I liked Hibernate so much I joined the project! So perhaps my opinion
is biased. ;)
[EMAIL PROTECTED]
