I am now in the phase of design and analysis of a software project. So i have to choose what should i use in this project.
For the presentation layer my candidates are Tapestry 3.0.3(because i don’t want to use Tap 5 who is still in alpha), ZeroKode (based from my recent experience) and Webwork (which i use in my last project).
I try ZK in the first place, and after a while i decide not to use it because of my lack of experience with this framework and the fact that i am working this project with my co-worker who only familiar with Tapestry, so goes out ZK. And without considering Webwork for the same reason, i choose Tapestry.
I use Spring as the middle layer to manage the beans. Because… it’s a clear choice 
Last is to choose the DAO layer.
The options are Hibernate, Ibatis or just simple JDBC. It’s a hard choice, i want a powerful tool but i don’t want to write too much of xmls, Tapestry 3 already have much xml to write.
I almost choose JDBC as my DAO layer, but then i read something in Spring 2 in Action.
…When we were kids, riding a bike was fun, wasn’t it? We would ride to school in the
mornings. When school let out, we would cruise to our best friend’s house. When
it got late and our parents were yelling at us for staying out past dark, we would
peddle home for the night. Gee, those days were fun.
Then we grew up and we needed more than a bike. Sometimes we have to
travel quite a distance to work. Groceries have to be hauled, and ours kids need to
get to soccer practice. And if you live in Texas, air-conditioning is a must! Our
needs have simply outgrown our bike.
JDBC is the bike of the persistence world. It is great for what it does, and for
some jobs it works just fine. But as our applications become more complex, so do
our persistence requirements. We need to be able to map object properties to
database columns and have our statements and queries created for us, freeing us
from typing an endless string of question marks…
So finally i see the option, Hibernate 3 with Annotation. Powerful tool yet less xml.
May all the choices were right and i can complete my project in 9 week.
Powered by ScribeFire.
