If you're interested in doing it, I think its fine. I'm not quite sure its the best usage of limited time :-)
On Thu, Jul 26, 2012 at 4:29 PM, Misagh Moayyed <[email protected]> wrote: > Speaking of annotations, I think applying the same approach to test > classes would merit some effort as well, and it's even easier given that > the test to test change(!) is already there to begin with :) > > -Misagh > > > > > -----Original Message----- > > From: Marvin Addison [mailto:[email protected]] > > Sent: Thursday, July 26, 2012 12:54 PM > > To: [email protected] > > Subject: Re: [cas-dev] CAS Roadmap 2012-2013 > > > > > I would also take this opportunity and add "modernizing the Spring > > MVC > > > layer" i.e. dropping the old Controller inheritance hierarchy > > > implementation and refactoring it with @MVC annotation style POJO > > controllers, etc. > > > > +1 > > > > I think it mostly amounts to code cleanup, so relatively little > > user/deployer value for what I imagine will a lot of dev/QA work. > > That said the reduced code/complexity may pay off in the long run for > > the relatively high up-front cost. > > > > M > > > > -- > > You are currently subscribed to [email protected] as: > > [email protected] To unsubscribe, change settings or access archives, > > see http://www.ja-sig.org/wiki/display/JSG/cas-dev > > -- > You are currently subscribed to [email protected] as: > [email protected] > To unsubscribe, change settings or access archives, see > http://www.ja-sig.org/wiki/display/JSG/cas-dev > -- You are currently subscribed to [email protected] as: [email protected] To unsubscribe, change settings or access archives, see http://www.ja-sig.org/wiki/display/JSG/cas-dev
