Howard Lewis Ship <hlship <at> gmail.com> writes: > For me, the issue is that this puts an onus on the developers (us!) to > write much more code for components, while limiting their > functionality in the process (locking down some parameters as simple > read-only properties).
Are you concerned that someone may change a parameter value when the component is rendering? > There's a lot of work involved in getting a parameter to work > properly, cache its value, reset at the end of the request, etc., > etc., that under the current system, is handled efficiently and > automatically with runtime bytecode generation. In the type safe setter style, the parameter values are cached in as properties. They are reset at the end of the request. The calls to the setter is compiled. What is missing? -- Author of a book for learning Tapestry (http://www.agileskills2.org/EWDT) --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
