>> This solves the problem, and you can do it automatically in your >> basecontroller class, if needed. I do not see any point to separate >> these namespaces. > > This seems like a hack to me.
I founded the same problem as Taavi about month ago and I did solve it 'the hack way'. For me it wasn't a hack. What is one wants that controller parameters are propagated to a view? What important features does the separating these contexts add to Maverick? For me it's ok to separate them and I don't mind if you refactor it. Just thoughts. Regards Aapo Laakkonen ------------------------------------------------------- This SF.NET email is sponsored by: FREE SSL Guide from Thawte are you planning your Web Server Security? Click here to get a FREE Thawte SSL guide and find the answers to all your SSL security issues. http://ads.sourceforge.net/cgi-bin/redirect.pl?thaw0026en [INVALID FOOTER]
