• 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 all forums
this forum made possible by our volunteer staff, including ...
Marshals:
  • Campbell Ritchie
  • Ron McLeod
  • Paul Clapham
  • Bear Bibeault
  • Junilu Lacar
Sheriffs:
  • Jeanne Boyarsky
  • Tim Cooke
  • Henry Wong
Saloon Keepers:
  • Tim Moores
  • Stephan van Hulst
  • Tim Holloway
  • salvin francis
  • Frits Walraven
Bartenders:
  • Scott Selikoff
  • Piet Souris
  • Carey Brown

SkillSet of Web Work

 
Ranch Hand
Posts: 390
  • Mark post as helpful
  • send pies
  • Quote
  • Report post to moderator
What do you think about the availability of those knowledgeable in this technology? In essence what would make a corporation to be favorable disposed to the usage of this framework?
 
Greenhorn
Posts: 10
  • Mark post as helpful
  • send pies
  • Quote
  • Report post to moderator

What do you think about the availability of those knowledgeable in this technology?


It would be hard for me to guage the current availability of people who are knowledgeable; however, I will found out soon as we are beginning to hire. What I do know is that bringing someone up to speed on WebWork is significantly than another technology, including Struts (yes, there are web developers who have never used Struts before). IMO, the core idea surrounding WebWork is the command pattern applied to POJOs.

In essence what would make a corporation to be favorable disposed to the usage of this framework?


I would look to the features on WebWork as to why a company should use is over another framework. Specifically:

  • Ease of unit testing. Remember, these are simple POJOs with setX() methods for incoming parameters, an execute() method to perform the action, and getX() methods to retrieve the result data
  • Utilize current knowledge base - WW supports JSP, Velocity, and Freemarker.
  • Abstraction from Request/Response and Servlet API. Typically, there is no need to deal with anything other than setters, getters, and Action execute methods.
  • Thread safe. Since each request instantiates a new action, all action execution is thread safe.
  • Action properties are directly accessible as regular Javabeans properties. This includes rich Object types which can have their own properties.
  • Model-Driven Approach. ModelDriven Actions allow a rich Object type or domain object.
  • There is a great book coming out


  • My issue with other web frameworks is that they aren't fully useful until you have an entire homegrown infrastructure to make things easier. With WebWork, I felt like we hit the ground after a minimal time intestment.


    Cheers,
    Matthew
     
    This is awkward. I've grown a second evil head. I'm going to need a machete and a tiny ad ...
    Thread Boost feature
    https://coderanch.com/t/674455/Thread-Boost-feature
      Bookmark Topic Watch Topic
    • New Topic