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 dataUtilize 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
