Bidvertiser

Sunday, August 9, 2009

Debate on best framework for developing JEE applications

Frameworks, Frameworks everywhere. Listing frameworks for developing JEE applications:
  1. Echo
  2. Struts
  3. RIFE
  4. JPublish
  5. Verge
  6. Action Framework
  7. Expresso
  8. OpenEmcee
  9. JWAA
  10. Smile
  11. Jeenius
  12. Dovetail
  13. Japple
  14. Nacho
  15. Click
  16. Cocoon
  17. SOFIA
  18. Spring MVC
  19. JATO
  20. Niggle
  21. Shocks
  22. Bento
  23. Turbine
  24. Jaffa
  25. MyFaces
  26. JWarp
  27. Cameleon
  28. Helma
  29. Cassandra
  30. GWT
  31. Millstone
  32. Tapestry
  33. Canyamo
  34. Folium
  35. Bishop
  36. TeaServlet
  37. jStatemachine
  38. Scope
  39. Jacquard
  40. Chiba
  41. Genie
  42. JFormular
  43. Dinamica
  44. Baritus
  45. OXF
  46. WebWork
  47. Maverick
  48. Jucas
  49. Barracuda
  50. wingS
  51. jZonic
  52. Warfare
  53. Macaw
  54. JBanana
  55. Melati
  56. Xoplon
  57. WebOnSwing
  58. Stripes
  59. JSF
May be more...
Introducing Wicket
JSP is by far the worst offender, allowing the embedding of Java code directly in web pages, but to some degree almost all of the frameworks from the list (except Tapestry) above introduce some kind of special syntax to your HTML code.
Special syntax is highly undesirable because it changes the nature of HTML from the kind of pure-and-simple HTML markup that web designers are familiar with, to some kind of special HTML. This special HTML can be more difficult to preview, edit and understand.
Wicket does not introduce any special syntax to HTML. Instead, it extends HTML in a standards-compliant way via a Wicket namespace that is fully compliant with the XHTML standard. This means that you can use Macromedia Dreamweaver, Microsoft Front Page, Word, Adobe Go Live, or any other existing HTML editor to work on your web pages and Wicket components.
A comment on struts
Struts is great for small to medium size application. When the application gets big, especially when presentation logic gets complicated, it is really a big hassle to maintain the a big xml config file. Also a problem to maintain a big properties file for message used all over the application.
This URL discusses on struts and introduces shine.
Too much frameworks, my take will be do not ignore any. Though we may not able to master many.
Struts vs JSF
A good article on Struts vs JSF. http://www.simplica.com/strutsvsjsf.htm
Choosing a java web framework
A comparison presentation given in 2008 javaone conference. http://developers.sun.com/learning/javaoneonline/2008/pdf/TS-6457.pdf
This blog by Manoj maniraj has few more important points to be considered while picking your framework.
Just put in your views on the best framework.

No comments:

Post a Comment