> The problem is context I guess. Usally your component depends on lots > of stuff. Parameters, URL, Services, Page-state, component state, > HTTP-Parameters and so on.
Yes...but it must be possible somehow as some PHP template engines also do it. Isn't there already some mechanism in the internals of Tapestry that keeps track of that even now? --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
