> I think that's quite enough, try servlets as well
I favor knowing how to tune a car before talking to the mechanic.
I'd start with JSP and servlets with Java Server Faces (JSF) and the Java
Persistence API. (I am just starting to learn the Persistence API. I
actually started with JSP, servlets, coding my own MVC framework and writing
my own data access framework.) That really makes one appreciate frameworks
like JSF, Struts, Persistence API, Hibernate or whatever, because now one
groks from first-hand experience what they're accomplishing.
Or failing to accomplish.
I've worked with people who knew the Struts API cold but didn't understand the
Model-View-Controller concept. It led to some peculiar choices.
I have doubts about many of these frameworks. I haven't used Hibernate, but I
worked on a project that used Torque, another "object-relational" framework.
Yecch. It's easier to just code PreparedStatements with JDBC. I found the
overhead of Torque egregious, and it restricted me from much of the power of
the database.

Signature
Lew
Snyke - 18 Aug 2007 19:58 GMT
> dimov.vla...@gmail.com wrote:
> > I think that's quite enough, try servlets as well
[quoted text clipped - 21 lines]
> --
> Lew
Way back I already used Hibernate for the persistence of the data onto
a relational db, and I found it quite good, as I spent a lot of time
manually mapping my php-objects to a database before. The problem is
that I want this application to be build on top of solid foundations
as it might grow over time, and I'm currently very interested in the
spring framework. I also used some MVC-Frameworks on client
applications and I feel pretty comfortable with it. As for the
tradeoff of ease to program and speed using Hibernate, yeah that might
be a problem later in the productive environment but as I understand
it, it shouldn't be too hard to exchange the persistence layer when
using Spring.
Anything I'm missing?
Regards,
Christian
--
http://www.snyke.net
Arne Vajhøj - 19 Aug 2007 02:53 GMT
> Way back I already used Hibernate for the persistence of the data onto
> a relational db, and I found it quite good, as I spent a lot of time
[quoted text clipped - 7 lines]
> it, it shouldn't be too hard to exchange the persistence layer when
> using Spring.
I think that Spring *and* Hibernate is a very common combination.
It is probably more common than any other Spring and database access
combination - including JdbcTemplate.
Arne