For the last 8 years I have been making a living as a consultant writing Java
applications. In that time, I have seen everything from no framework (just Servlets
, and Spring.
As a consultant I have always wanted to deliver results to the client, not waste my time writing code or xml to make other code work. I thought that was what a Framework was supposed to do!
I had never heard of Stripes until a co-worker paired with me last January and introduced me to it. I had been reading Pro EJB
3.0 and was very interested in JPA even though I had no prior EJB experience. We created from scratch, in about an hour, a database web app using EJB 3.0 on JBoss
with Stripes and Guice for dependency injection. If you asked me to write the Guice piece again, I could not. But that is because we wrote it once (an interceptor, some web.xml entries) and then forgot about it. I just know that when I wanted to inject a Model Bean into my Action Bean I would write @Inject and the Bean name.
Since then I have moved on to another LARGE client but to a very small team. I was asked to write a new app and pick my framework. I chose Stripes. I was able to complete that app relatively painlessly using just the framework, some JSPs, and EL. I used no Ajax or reusable layouts or Guice injection - none of the bells and whistles. The documentation on the web site seemed to be, like most docs on open source projects, written to the level of the developers building the project. I HATE THAT. If I understood as much as those guys, I�d be writing books too. They constantly make assumptions that you just �know� how to configure stuff. Sorry guys, but when I�m learning a new framework and some �obvious� details are left out and I can�t get it to work after a reasonable amount of time, I drop it.
Well my boss liked the Stripes app so much he started asking me about the bells and whistles. I told him what was possible and they asked me to plan on replacing their very complicated home grown framework with Stripes. Honestly, I knew what was possible but I didn�t know how I was going to learn it and deliver.
Then this book came out.
I ordered the PDF and the book and started working immediately with the PDF, building the sample app. Then the book came and things got even easier. (Just something about reading a book on the train that helps things sink in better, I guess.)
Long story short, today I started replacing all of the clients Dreamweaver templates, with the much more concise Stripes reusable layouts. I am eliminating a ton of redundant code and introducing Stripes to the app. Along the way I have been able to get questions answered quickly on the mailing list and by Freddy directly. When I�m done with those I will start on the Action Beans. Bottom line: if I can, with the help of this book, get Stripes up and running in minutes, integrate Ajax, Hibernate, and reusable layouts shortly after, then you can too.