Discussions

News: Don Brown on Unification of Struts Action and JSF

  1. In "Unification: Struts Action and JSF," Don Brown says that "Struts Action 2 has builtin support for JSF, using an approach that smoothly combines both frameworks into one configuration file, one framework." The JSF components still have access to the entire JSF lifecycle while retaining the action-based paradigm. An example of the JSF/Struts Action configuration file looks like this:
    index
    Don points out that action-based frameworks and component-based frameworks don't have to compete:
    The bottom line is Struts Action 2 proves it is possible for the action-based and component-based frameworks to work together, and application developers no longer have to choose one or the other exclusively. They can make the decision on a page-to-page basis according to its particular requirements. Enough of these "web framework wars", and let's move on to more interesting problems. :)
    As one constantly caught in the conflict between component- and action-based frameworks, this might be the "killer framework" that solves most problems. What do you think?
  2. In "Unification: Struts Action and JSF," Don Brown says that "Struts Action 2 has builtin support for JSF, using an approach that smoothly combines both frameworks into one configuration file, one framework." The JSF components still have access to the entire JSF lifecycle while retaining the action-based paradigm.

    An example of the JSF/Struts Action configuration file looks like this:




    index
    Don points out that action-based frameworks and component-based frameworks don't have to compete:
    The bottom line is Struts Action 2 proves it is possible for the action-based and component-based frameworks to work together, and application developers no longer have to choose one or the other exclusively. They can make the decision on a page-to-page basis according to its particular requirements. Enough of these "web framework wars", and let's move on to more interesting problems. :)
    As one constantly caught in the conflict between component- and action-based frameworks, this might be the "killer framework" that solves most problems. What do you think?
    Jacob Hookom has had a very good entry on the subject couple of months ago, which explain the idea : http://weblogs.java.net/blog/jhook/archive/2006/03/the_new_servlet_1.html
  3. Don took a different approach with this, but I'm very happy that he was able to prove that the collaboration/use of the JSF API was implementatable.