Good question Joey. My first reaction was going to be no: I don't want to add method declarations that aren't required to the code templates. Then I realized we already have two in there: getDefaultView() and getRequestMethods()... Granted, those two methods are a lot more likely to need to be modified than isSecure() or getCredential() I'd think.
That said, we also use both extensively in our work, so I guess I could be convinced to add them in. Maybe a better solution would be to think about how Agavi could allow you to specify custom templates to be used, rather than our stock ones. (or just modify the stock ones..) (??) What does everyone else think? --Bob On 7/30/05, Joe Cai <[EMAIL PROTECTED]> wrote: > Hi,there > Sometimes we do need ActionClass::isSecure() or > ActionClass::getCredenttial() ,how about adding them to the class > template so that we don't have to do such thing by hand:) > -- > Regards, > Joe > _______________________________________________ > agavi-dev mailing list > [email protected] > http://labworkz.com/cgi-bin/mailman/listinfo/agavi-dev > _______________________________________________ agavi-dev mailing list [email protected] http://labworkz.com/cgi-bin/mailman/listinfo/agavi-dev
