I was just flipping through the docs. It looks like a better version of Struts. We seem to be adding some features in parallel (he just added conversion of paramters to object types, for example).
His metaphor is a bit different. Somewhat less use of properties, and the "value stack". For example, in Tapestry, the Foreach components takes as an input parameter a list of objects then iterates through them. For each value in the list it will optionall store the value to a property of its container (via a parameter) then render its body. Components inside its body can get the current value from the container property, or can get the current value from the Foreach (i.e., a property path of "components.foreach.value"). In WebWork, the controller will have pushed the list (or an object containing the list) onto the value stack. The Iterator tag will get the list from the value stack and start iterating. On each iteration, it pushes the current value onto the stack and pops it off at the end of the iteration. It appears that the value stack is the main metaphor for seperating controller logic from presentation logic; apparently, controllers (the equivalent of listener methods) get the value stack in some state and can manipulate it before passing control to a view. In this way (I guess) the same controller can operate in disparate environments, such as Swing GUI or JSP or Velocity. The stack approach is interesting, since it supports some kind of controller chaining and the seperation. Anyone have more knowledge? I (obviously) still prefer the Tapestry approach: Objects, methods and properties. The equivalent WebWork mantra would be "value stacks and actions". Side note: there are people who bitch and moan about all the XML specifications in Tapestry ... yet whenever I look at a "simpler" solution based on JSP and tag libs ... well, there's way, way more wierd markup inside the JSP than would ever been in a Tapestry specification. This applies to WebWork as well ... there was a forms example that just had reams of stuff in the JSP. This was also pointed out at the Boston user's group where I presented Tapestry ... in Tapestry each file contains just one language: all HTML, or all Java or all XML. -- [EMAIL PROTECTED] http://tapestry.sf.net ------------------------------------------------------- This sf.net email is sponsored by: OSDN - Tired of that same old cell phone? Get a new here for FREE! https://www.inphonic.com/r.asp?r=sourceforge1&refcode1=vs3390 _______________________________________________ Tapestry-developer mailing list [EMAIL PROTECTED] https://lists.sourceforge.net/lists/listinfo/tapestry-developer
