I'll try to explain what RenderAction does in MonoRail terms:
Let's say there's a method in HtmlHelper called RenderAction. This
method takes the same parameters as UrlHelper.For(), so you would call
it like this (brail):
${Html.RenderAction({...@controller: 'user', @action: 'view',
@querystring: 'id=2'})}
What this does, when called from a view, is execute the View() action
in UserController, binding the @querystring parameters, capture the
rendered output and place it in the view where the RenderAction() call
was.
With this, there can be multiple actions executing within the same
http request. It's nice for neatly separating concerns, as in
http://www.lostechies.com/blogs/jimmy_bogard/archive/2009/06/18/the-filter-viewdata-anti-pattern.aspx
--
Mauricio
On Aug 18, 10:26 am, "R. Rajesh Jeba Anbiah"
<[email protected]> wrote:
> On Aug 17, 12:07 pm, Martin Nilsson <[email protected]> wrote:
>
> > It's ViewComponents that you are looking
> > forhttp://www.castleproject.org/MonoRail/documentation/trunk/usersguide/...
>
> Unfortunately, no. I want the view contents to be processed or
> undergo processing from controller & model.
>
> --
> <?php echo 'Just another PHP saint'; ?>
> Email: rrjanbiah-at-Y!com Blog:http://rajeshanbiah.blogspot.com/
--~--~---------~--~----~------------~-------~--~----~
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
-~----------~----~----~----~------~----~------~--~---
