The best approach might be to read the source code and the documentation together. The documentation does refer to the major components along the way, and as it does, bring up the source code and review that too. To setup the source in your editor, ready to compile, see
* http://struts.apache.org/2.x/docs/building-the-framework-from-source.html What we have on the "big picture" is in the Architects Guide. You could also use that as a roadmap for reading the source. * http://struts.apache.org/2.x/docs/big-picture.html For the core framework, one entry point would be the FilterDispatcher, that exposes the framework to the container. * http://svn.apache.org/viewvc/struts/struts2/trunk/core/src/main/java/org/apache/struts2/dispatcher/FilterDispatcher.java?view=log The tag code starts in the Views package * http://svn.apache.org/viewvc/struts/struts2/trunk/core/src/main/java/org/apache/struts2/views/ and ends in the Resources folder * http://svn.apache.org/viewvc/struts/struts2/trunk/core/src/main/resources/ If you'd like to pass along any insights to others who might be interested in the architecture, please feel free to post material here or to the wiki. * http://cwiki.apache.org/S2WIKI/home.html -Ted. --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
