We're looking into using Spring right now but its currently up in the air whether we'll use Struts or JSF with Kodo JDO. Anyone have any experiences with these and any recommendations/pitfalls to avoid?
Right now, Spring and Struts are probably a better fit because a lot of people have been/are working with that combination while JSF is still pretty much a thing of the (near) future. Having said that, and as a strictly personal opinion, I'd recommend avoiding Struts and going with JSF. The Struts Action/ActionForm architecture doesn't go well with my preferences. Your mileage may vary, of course.
I believe we're leaning towards Struts but I'd for one like to see JSF myself. I've been reading up on JSF and it appears to be "Struts on Steroids". Hopefully it won't suffer the consequences of being juiced up.
FWIW, I'm working on a project right now using JSF, and I'm thinking about using Spring as the back end if I can be convinced of its worth and ease of integration with JSF (I hear "oh yeah it can be done" but I haven't seen a good explaination of HOW it IS done).
BTW, for JSF, I'd strongly suggest you look into Java Studio Creator...talk about EASE of development. Really nice tool IMHO...a little slow maybe, but it sure makes up for it in what it gives you (think drag and drop JSP).
Joined: Jan 23, 2002
Originally posted by Darrin Smith: FWIW, I'm working on a project right now using JSF, and I'm thinking about using Spring as the back end if I can be convinced of its worth and ease of integration with JSF (I hear "oh yeah it can be done" but I haven't seen a good explaination of HOW it IS done).
Well, as far as I can tell (based on reading chapter 10.3 from Spring in Action) there's not much to integrate... Basically you put your model object into the request, let JSF tags generate the UI, and JSF invokes your model object's "submit" method upon form submit. The Spring stuff comes into the picture in doing what you want to do when that submit call comes.
I have bean making a prototype with JSF. It was much more difficult then I expected. I have 4 years Struts experiences but JSF and JSTL are quite different to us. In the current project we choose know to use Tapestry , Spring and Hibernate. A prototye was made much faster and easier even Tapestry works bit different. I think it is a very good framework and has many advantages like your pages are readable by standart html development tool like dreamweaver.
I am actually running the combination you are evaluating (Spring+Struts+Kodo) and so far everything runs pretty well. With some help of Matts Book and the KodoJDO Spring Example application, i was able to get a first running CRUD app within two days.
So i can recommend this combination. But i am also quite new to Spring and i am definitely not a Spring Pro at this very moment.
I guess if I were in your position I would be talking about Spring MVC or JSF or Tapestry - not Struts. Not that there is anything particularly wrong with Struts, but in my mind Spring MVC just feels better.
JSF and Tapestry are both excellent frameworks and can be backed with a Spring-based middle tier. There seems to be a lot of FUD surrounding JSF and to a lesser degree Tapestry, but my experiences with both have been excellent - I think the main problem is that they are very different to what we are used to in the Java world and they are much closer, conceptually, to ASP.NET.
I guess if you are just adopting Spring for the first time, then pick the web framework you know. There is no reason to try to use two new frameworks - that will just add unnecessary complexity to your project.