Thiago is right; it's more like a pipeline, although not exactly a pipeline, either. :) It's still a state machine, stepping through the various render phases, but in each render phase, you have a series of "sub states", one for each mixin, + the component's own method. In 5.2, you can explicitly define the order of execution to make sure your mixin executes before any others, etc. (all of the commands supported by OrderedConfiguration are supported). And in 5.2, you can directly access a component's parameter from within the mixin, even if the component's parameter doesn't have a public getter.
Robert On May 13, 2010, at 5/133:15 PM , Thiago H. de Paula Figueiredo wrote: > On Thu, 13 May 2010 17:09:45 -0300, Andreas Bohnert <a...@weberhofer.at> > wrote: > >> this looks very promising!! >> that is what I was asking for and would solve at least my problem :) >> >> So with mixins you do/can not override a method, you build a execution chain >> instead? > > In a simplified view, mixins work like you had copied their methods to the > component or page to which the mixin is applied. I wouldn't say it's an > execution chain. This sounds more similar to Tapestry-IoC's pipelines. > > -- > Thiago H. de Paula Figueiredo > Independent Java, Apache Tapestry 5 and Hibernate consultant, developer, and > instructor > Owner, Ars Machina Tecnologia da Informação Ltda. > http://www.arsmachina.com.br > > --------------------------------------------------------------------- > To unsubscribe, e-mail: users-unsubscr...@tapestry.apache.org > For additional commands, e-mail: users-h...@tapestry.apache.org --------------------------------------------------------------------- To unsubscribe, e-mail: users-unsubscr...@tapestry.apache.org For additional commands, e-mail: users-h...@tapestry.apache.org
