• Post Reply Bookmark Topic Watch Topic
  • New Topic
programming forums Java Mobile Certification Databases Caching Books Engineering Micro Controllers OS Languages Paradigms IDEs Build Tools Frameworks Application Servers Open Source This Site Careers Other Pie Elite all forums
this forum made possible by our volunteer staff, including ...
Marshals:
  • Campbell Ritchie
  • Jeanne Boyarsky
  • Ron McLeod
  • Paul Clapham
  • Liutauras Vilda
Sheriffs:
  • paul wheaton
  • Rob Spoor
  • Devaka Cooray
Saloon Keepers:
  • Stephan van Hulst
  • Tim Holloway
  • Carey Brown
  • Frits Walraven
  • Tim Moores
Bartenders:
  • Mikalai Zaikin

New project - what do I use?

 
Greenhorn
Posts: 21
  • Mark post as helpful
  • send pies
    Number of slices to send:
    Optional 'thank-you' note:
  • Quote
  • Report post to moderator
Hello,

I am about to start on a new J2EE project. I have developed using JSPs and servlets in the past and recognise the benefits of frameworks so which one should I use JSF, Struts or Tapestry?

As I understand it JSF is new so could it be risky and the IDEs are immature. Whereas Struts is established.

Any guidance would help.

Many Thanks,

Shaun
 
Sheriff
Posts: 6450
  • Mark post as helpful
  • send pies
    Number of slices to send:
    Optional 'thank-you' note:
  • Quote
  • Report post to moderator
My own personal opinion, which I suppose may be biased because I am not all that familiar with Tapestry and JSF, is that right now Struts is a safe bet in general. If you are having to learn a new framework, you will find more information available on Struts than the others as well as several good books. Most importantly imho, you are more likely to find people on your development team who are already familiar with Struts in addition to the fact that you are more likely to run into other projects using Struts compared to the other two right now (therefore increasing the chances that you will re-use your Struts knowledge). That's just my own two cents, and other factors may certainly weigh on your decision. Maybe some reps from the JSF and Tapestry corners can add to this discussion.
 
Author
Posts: 106
  • Mark post as helpful
  • send pies
    Number of slices to send:
    Optional 'thank-you' note:
  • Quote
  • Report post to moderator

Originally posted by Shaun Appleton:
Hello,

I am about to start on a new J2EE project. I have developed using JSPs and servlets in the past and recognise the benefits of frameworks so which one should I use JSF, Struts or Tapestry?

As I understand it JSF is new so could it be risky and the IDEs are immature. Whereas Struts is established.

Any guidance would help.

Many Thanks,

Shaun




I'll let Howard tell you about Tapestry, but between Struts (with plain JSP) and JSF, you should use the one with the features the application need.

Easier said than done, I know, but if the user interface is simple (and you're not into using RAD tools) but the backend is fairly complex, Struts may be a good choice. If the user interface is complex (or you want to use RAD tools and can wait until the end of the summer), JSF may be a good choice. If the user interface is complex but there are also Struts features your application desperatly needs, you may consider the Struts-JSF integration package and use both.

JSF is new, so it's not as stable as Struts or Tapestry, but I think that will change soon given the broad industry support. Still, if the project needs to be finished this fall, you should probably take this into account before picking JSF.

My general advice is to read up on all three and play around with them to see which one is the best fit for the application.
 
Ranch Hand
Posts: 83
  • Mark post as helpful
  • send pies
    Number of slices to send:
    Optional 'thank-you' note:
  • Quote
  • Report post to moderator
hi,
take one of the sample applications of struts and use this as your starting point. This will already give you a headstart on the learning curve that you will undoubtedly have.
Then depending on your user interface (whether you want a rich user interface or a boring one ;-) you can decide if you want to use jsf. I assume you can plug in jsf at a later date as well and use it only on the places where it adds something. At least take a look at the possibilities of jsf.

Besides this advice, you may want to start the project with a prototype, giving you a few weeks to read up.
 
"Don't believe every tiny ad you see on the internet. But this one is rock solid." - George Washington
a bit of art, as a gift, the permaculture playing cards
https://gardener-gift.com
reply
    Bookmark Topic Watch Topic
  • New Topic