I see, we are actually talking about "state in page" vs "state in component" approaches.
>> the component encapsulates the knowledge about specific >> url parameters that it needs > So given the above this appears to me to be paradoxical, if you are going to > encapsulate the url parameters then you do not need to expose an external > event method, something you can achieve with parameters for instance. I mean encapsulate the component state from the page. It can save some boilerplate code when you reuse the component on a lot of pages. Also when the activation context is not simple it can be more clearly expressed when spread over (some parts of ) the component tree. My 2 cents :) --------------------------------------------------------------------- To unsubscribe, e-mail: users-unsubscr...@tapestry.apache.org For additional commands, e-mail: users-h...@tapestry.apache.org
