Hi John, adding my 2 cents,
I think this is here to support people who overidded Controller.SelectMethod, I've almost nothing against removing it myself but I'm not sure it will suit everybody. The only problem I have is that actionSelector is not read/write accessible as protected from controllers, and it's provided from MR service factory without having any place to switch implementation according to different contexts. Since I don't have a simple solution for those relying on overriding Controller.SelectMethod, I'm not for rushing it's removal, but to work out a easy migration path. Providing a way to bypass/replace actionSelector instance initialization might be a solution. On Jul 8, 8:52 pm, John Simons <[email protected]> wrote: > I came across the following comment in MR > src:http://github.com/castleproject/Castle.MonoRail/blob/master/src/Castl... > > Just wondering if anyone remembers this change and if the way forward is to > get > rid of the old way of doing this in favor of the new way? > > Cheers > John -- You received this message because you are subscribed to the Google Groups "Castle Project Development List" group. To post to this group, send email to [email protected]. To unsubscribe from this group, send email to [email protected]. For more options, visit this group at http://groups.google.com/group/castle-project-devel?hl=en.
