I've been thinking that I want to change the <inject-state> element into something more generalized.
I was just thinking about how cool it would be to be able to inject a compiled script template (an IScript instance). The approach would be similar to injecting state. This it hit me, that these are two different strategies, so. <inject-state property="foo" object="visit"/> Would become: <inject-special property="foo" type="state" value="visit"/> And we could add: <inject-special property="foo" type="script" value="MyScript.script"/> .... then I realized that <inject> is itself just a special case, where the type is, for example, "object" (meaning, an object resolved using HiveMind).. So we can just make "object" the default for type and do-away with <inject-state> (and <inject-special>), i.e. <inject property="request" value="infrastructure:request"/> <inject property="visit" type="state" value="visit"/> <inject property="script" type="script" value="MyScript.script"/> Thoughts? -- Howard M. Lewis Ship Independent J2EE / Open-Source Java Consultant Creator, Jakarta Tapestry Creator, Jakarta HiveMind Professional Tapestry training, mentoring, support and project work. http://howardlewisship.com --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
