Hi Actually, there is no problem if you do that since you generate a valid action URL of your form and use request service to read parameter values.
But this is not how Tapestry has been designed, Tapestry is a component oriented framework, not an action oriented framework. Static structure simply means that you cannot create *new* instances of component at runtime. That does not mean that you as a developer can't go beyond this principle and use Request.getParameter() method or even generate plain HTML in dom tree But if you use Tapestry components, you must be aware that even if you put a component inside a loop, the inner component will be 'rendered' n-times but ultimately there is only ONE instance of this component. 2010/10/5 iberck <ibe...@gmail.com>: > > Hi, thank you for the response > > So I don't understand the principle > > 1. What happend if I add a html element in the tree dom and I get the value > from the request after submit ? > I'm violating the principle? > > Is there a problem if I do that? > > > -- > View this message in context: > http://tapestry.1045711.n5.nabble.com/T5-2-Principle-1-Static-Structure-Dynamic-Behaviour-tp3198357p3198857.html > Sent from the Tapestry - User mailing list archive at Nabble.com. > > --------------------------------------------------------------------- > To unsubscribe, e-mail: users-unsubscr...@tapestry.apache.org > For additional commands, e-mail: users-h...@tapestry.apache.org > > -- Regards, Christophe Cordenier. Committer on Apache Tapestry 5 Co-creator of wooki @wookicentral.com --------------------------------------------------------------------- To unsubscribe, e-mail: users-unsubscr...@tapestry.apache.org For additional commands, e-mail: users-h...@tapestry.apache.org
