# What is the best way to reuse a controller's action and views?

**URL:** <https://www.ruby-forum.com/t/what-is-the-best-way-to-reuse-a-controllers-action-and-views/128294>\
**Category:** Rails\
**Created:** [February 6, 2008, 2:54pm UTC](https://www.ruby-forum.com/t/what-is-the-best-way-to-reuse-a-controllers-action-and-views/128294 "2008-02-06T14:54:08Z")\
**Posts on this page:** 1\
**Page:** 1

<div class="post-metadata">

**Author:** ![Hendy\_I](https://www.ruby-forum.com/letter_avatar_proxy/v4/letter/h/b4bc9f/32.png) [@Hendy\_I](https://www.ruby-forum.com/u/Hendy_I)\
**Post date:** [February 6, 2008, 2:54pm UTC](https://www.ruby-forum.com/t/what-is-the-best-way-to-reuse-a-controllers-action-and-views/128294/1 "2008-02-06T14:54:08Z")

</div>

On Jan 25, 2008 10:36 PM, removed\_email\_address@domain.invalid \<  
removed\_email\_address@domain.invalid\> wrote:

> Check out RailsEngines: [http://rails-engines.org/introduction](http://rails-engines.org/introduction)

Have to agree on the RailsEngines.

If your views are non-changing then you may consider a combination of:

- generator script to generate views and controllers
- the controllers are actually ‘dumb’ ones that simply include a  
module(s)
- the module(s) are in the plugin, including the Rails generators