• 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

ActionForm bean decision

 
Ranch Hand
Posts: 339
  • Mark post as helpful
  • send pies
    Number of slices to send:
    Optional 'thank-you' note:
  • Quote
  • Report post to moderator
Hello, there! programmer comrades !

I have witnessed the evolution of Struts, and I consider it the best implementation of the MVC Design pattern for Web Apps, but I always felt that having to Associate every Struts Action to a FormBean was kinda 'clumsy'.
I understand now that in Struts 2, they have supressed the FormBeans...
Do you think that was a wise decision? or was there actually a specific purpose for the Bean to carry out?

And I suppose this means that the XML structure of the struts-config.xml, has also been changed... Is it now Simplified ?

I hope my question is worthy of your time,

Sincerely,
Jose
 
reply
    Bookmark Topic Watch Topic
  • New Topic