On 9/26/01 11:55 AM, "Jon Stevens" <[EMAIL PROTECTED]> wrote:
> on 9/26/01 6:34 AM, "Attila Szegedi" <[EMAIL PROTECTED]> wrote:
>
>> - BTW, is it any good having a template engine being able to call setXxx
>> methods, thus potentially altering underlying data (or business) objects?
>>
>> Attila.
>
> Yes. The reason why is that whatever you put into the Context, you have
> control over. Therefore, the setXxx methods that you make available are
> methods that you intended people to be able to use.
I agree more with Attila here. My particular opinion but I think #set is a
bad thing to put in a template for a webapp. I would even go so far as to
say that objects placed in the context for use in a webapp should be read
only.
I believe that a designer shouldn't modify anything objects used in an
application, and again it's my opinion but I don't buy the template engineer
designation.
> -jon
--
jvz.
Jason van Zyl
http://tambora.zenplex.org
http://jakarta.apache.org/turbine
http://jakarta.apache.org/velocity
http://jakarta.apache.org/alexandria
http://jakarta.apache.org/commons
