> 1) Is tapestry 5.3 a good choice for a site, where 2 o 3 web > developers will be developing?
It depend on who your "Web developers" are, their capabilities/preferences. Some people will really love Tapestry and some will not. Some people really need it to be X for them and get frustrated when it's not. Not every framework will work for everyone. Some people amazingly will prefer to try and write stuff from scratch instead of using a framework at all! Working together is going to depend on your teams ability to divide and conquer the tasks. Like in any project it's going to be painful if you have two people trying to concurrently edit the same page/component etc. > 2) I'm NOT an expert in tapestry, and I know the "static structure, dynamic > behavior" has some limits, which are this limits? Presumably you've read: http://tapestry.apache.org/principles.html "Static Structure" means that you don't change the page's model at runtime. You have to define the components you're going to use in the template or pojo. I have never found this to be a limit in the work that I've done. > 3) Finally, in the future, in my job I will need some widgets that > could use ajax, is hard to accomplish this? (in struts2 is really easy) Tapestry has a lot of ajax functionality built in. lt's evolving and getting better. You are likely going to come across areas that require you to built something custom. My advice is don't try to learn tapestry's ajax architecture by trying to implement the most complicated parts of your project first. Use tapestry source as a guide. I don't find it hard to do this anymore, but I've been doing it for a while now. On Sun, Sep 11, 2011 at 6:25 AM, Wechsung, Wulf <wulf.wechs...@sap.com> wrote: > For one, components are basically singletons so you can never have the same > component twice on the page. You can have it render twice with different > parameters which can accomplish the same thing but makes it necessary to > careful manage the components state. > This is all wrong. You get an instance of the component per occurrence in the template. If you put your component in a loop then it only exists in the model once but renders multiple times. This is two instances of the component. <t:pagelink t:id="pageone" .../> <t:pagelink t:id="pagetwo" .../> This is one instance of the component rendered 5 times. <t:loop source="1...5"> <t:pagelink t:id="pagethree" .../> </t:loop> Josh --------------------------------------------------------------------- To unsubscribe, e-mail: users-unsubscr...@tapestry.apache.org For additional commands, e-mail: users-h...@tapestry.apache.org
