Dear Wiki user, You have subscribed to a wiki page or wiki category on "Tapestry Wiki" for change notification.
The following page has been changed by ErikVullings: http://wiki.apache.org/tapestry/TapestryFasttrackForStrutsProgrammers ------------------------------------------------------------------------------ - = Tapestry Fasttrack for Struts Programmers = + = Tapestry Fast Track for Struts Programmers = + + This documentation serves as a high level resource to help Struts programmers to understand differences between Struts and Tapestry (3.0). = Foreword = + I have been a Struts programmer for a couple of years and I'm now looking for the next technology in web user interface development. While JSF sounds promising, it is still too early to commit to it IMO. Before diving into Struts years ago, I have looked at Tapestry and found myself unable to understand it. At that time, I'm just like everyone else, coming from a CGI programming background, that's why Struts seems to be a relatively easy framework to understand. A couple of years has passed and now I'm looking into Tapestry and find that it all makes sense! Hopefully, this article illustrates the similarities and differences between the two frameworks. + + PS. I'm a Tapestry newbie, so please if you find anything incorrect, inaccurate or needs to be further explained, you are encouraged to correct it, or email me so I can correct it ([EMAIL PROTECTED]). + = Architecture Comparison = - = Similarities = + Struts is based on the HTTP model (or more accurately Sun's Servlet API). The core idea is using the Struts controller servlet and its configuration file (struts-config.xml) to examine URLs (or HTTP form posts), instantiate a java bean (subclass of Action``Form) and set its properties using the URL parameters (or HTTP form post), invoke data validation method defined within the Action``Form, and then pass it along to a java class (subclass of Action or Lookup``Dispatch``Action) defined within the Struts configuration file (struts-config.xml) and finally looks up and dispatch to a destination view, typically a jsp page (there are other view technologies that are compatible with Struts, please refer to the Struts web site for more information). So it should be fair to say that Struts is action oriented (URL.do -> action.java -> destination.jsp). - = Differences = + Tapestry takes a slightly different approach. The architecture centered around the page. + = Comparisons = + + This section attempts to roughly compare the similarities and differences between the 2 frameworks. + + == Conceptual Comparison == + + === Struts modules vs. Tapestry application === + + === Taglibs vs. Tapestry Components === + + === Jsp vs. HTML Template === + + == Developmental Comparison == + + === struts-config.xml vs. app.application === + + === Jsp vs. page.html + page.page === + + === ActionForm.java + Action.java vs. page.java === + + === Form initialization === + + === Form validation === + + === Localization === + + = Conclusions = + --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
