I have a magical controller which is designed specifically so it
doesn't have any actions, but instead allows views to be "viewed"
because there's never going to be any data passed to the view as
follows:
public void DefaultAction()
{
string template = "NotFound";
if(HasTemplate(string.Concat(this.ControllerContext.Name,
"/", Action)))
{
template = Action;
}
PropertyBag["title"] = template;
RenderView(template);
}
It's not *that* magical.
Anyhow, when I use <?brail OutputSubView('Documentation') ?> nothing
happens on only those routes that are rendering a view template. So,
for example, on Documentation/Index OutputSubView will work just fine,
because it's a concrete implementation (I mean, code exists for that
view in the controller) where as any other routes, for example
Documentation/General which isn't concrete in that it uses
DefaultAction, will cause OutputSubView to simply not work at all.
This doesn't seem right to me, and in my case causes problems because
I don't want to have explicit actions, but I do want to be able to
render views, and I also want to be able to use OutputSubView simply
because I have a sidebar which allows you to navigate the
documentation.
Any hints on how else I could approach this problem? Or perhaps this
is a bug?
--
You received this message because you are subscribed to the Google Groups
"Castle Project Users" 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-users?hl=en.
