On Sunday 19 July 2009 10:16:59 pm Dimitrios Christodoulakis wrote: > > 2) If one with general knowledge of servlets & jsp wants to dive into > the struts2 source code, to get better understanding of the basic > mechanics, what would be the starting point? So should I start lets > say with the struts.core package?, which would be the entry point > class Despatcher, then ActionProxy? -- To the untrained eye (myself), > when looking the code from a distance > (http://svn.apache.org/viewvc/struts/struts2/trunk/core/src/), it > looks somewhat like a ball of twine, so where should I look for the > piece of string that sticks out and will help me untangle it? >
Depending on your goals, I think one place to start might be the xwork core. Xwork is an implementation of the command design pattern... http://en.wikipedia.org/wiki/Command_Pattern Once you have a solid understanding of what is going on within xwork, then you can start with the Dispatcher. That being said, Struts is really the combination of many things. For instance, it lets xwork drive the core flow of request processing, but there is also the tag library. The tag library does a good job of breaking up processing into models, templating and jsp tag specific stuff. If you are interested in the tag library, start with Component and take a look at a few of the easier to follow tags (s:if, s:url, etc.). Part of understanding the tag library means learning freemarker, but freemarker is easy to learn as you go. -Wes -- Wes Wannemacher Author - Struts 2 In Practice Includes coverage of Struts 2.1, Spring, JPA, JQuery, Sitemesh and more http://www.manning.com/wannemacher --------------------------------------------------------------------- To unsubscribe, e-mail: user-unsubscr...@struts.apache.org For additional commands, e-mail: user-h...@struts.apache.org
