• Post Reply Bookmark Topic Watch Topic
  • New Topic

Retrofit older apps with struts or jsf?  RSS feed

 
Michael Sullivan
Ranch Hand
Posts: 235
  • Mark post as helpful
  • send pies
  • Quote
  • Report post to moderator
First a little background, then my questions. My company has two geographically separated locations with J2EE applications. One uses IBM Websphere with struts, while the other uses Resin with plain MVC. Recently we had an 'in house' training session that demonstrated the struts framework, and recommended its use.
1. Being that our resin apps use neither struts or jsf currently, does it make sense to start developing in struts going forward, just to switch to JSF in 6 months/ 1 year?
2. Should we retrofit existing J2EE apps with one of these technologies, or impliment them going forward?
3. Since Struts is mature, and JSF is 'the new kid' should we just standby until JSF matures a bit before trying to impliment?
If JSF is very similar in benefits and implimentation to Struts, I'd like to forego struts-however I'm wary of an immature technology. That said:
4. Given the situation (where we can choose Struts versus JSF), which would you recommend for new and existing applications?

I thank you for your time and answers!
Michael
[ March 03, 2004: Message edited by: Michael Sullivan ]
 
Bill Dudney
Author
Ranch Hand
Posts: 234
  • Mark post as helpful
  • send pies
  • Quote
  • Report post to moderator
Hi Michael,
I'd say that if you have a time horizon of 6 months or more JSF is a viable option. If you production dates are before that I'd go with Struts.
I would not retrofit existing running apps with JSF unless there is a need. 'If it aint broken don't fix it' as the saying goes Oracle will be doing JSF via its ADF UXI framework which is mature. I can't speak to IBM's implementation.
I hope this helps!
 
  • Post Reply Bookmark Topic Watch Topic
  • New Topic
Boost this thread!