Cool thanks for all the feedback. I think for now I'll just dig into the
lower level stuff myself. I'm just going to use the java.sql classes, and
handle things that way. I really don't have much data to store in the
database at this point anyway. Already since I am using the command
pattern
>It sounds like hibernate, when integrated into my app, allows me to avoid
>having to worry about the lower level
SELECTs & parsing results etcetc?
That is true for the most part but as Charlie said it's not a pure win
because getting it to do what you want, how you want it to do it can
be very
I've used hibernate extensively and have had serious issues with it. The
actual SQL code is all generated auto-magically which can lead to problems.
I much prefer IBATIS, where the SQL is plainly visible and editable, and you
still get simple POJO manipulation. IBATOR can generate most of the sq
Thanks for the information.
I feel fairly comfortable with GWT and GWT-RPC now. I implemented the
command pattern & MVP pattern as per Ray Ryans talk, for my communication
over RPC. That gave me a pretty good crash course! I am sure there are
details in there I'll be learning along the way tho
I dont have any tutorials at hand but your understanding of where the
DB code lies is correct. It's totally on the server side and has
nothing to do with GWT. Your GWT app would get access to the data via
RPC. The RPC methods would in turn get data from the DB.
Hibernate is an ORM (object rela
I am writing a fairly large web app using GWT in Eclipse.My background
is as a c++ desktop developer, so while I have used java before, sometimes I
stumble on easy stuff.
Anyway, I am currently attempting to implement a database to store data from
my webapp. I am far from an expert in SQL, b
