Routes in Engines

I had remembered pondering this myself, and it is likely that several
may have as well.

I haven’t tested this yet, but I am under the impression throwing this
inside of a /vendor/plugins/my_engine/lib/routes.rb, very well may work.

It would be great to create an abstract layer ontop of the Rails engines
define new routes. Such as: “#{ADMIN_PAGE_DIR}/*name”,

Here is the snippet:

ActionController::Routing::Routes.draw do |map| map.connect
“#{ADMIN_PAGE_DIR}/*name”, :controller=>‘view_pages’,
:action=>'show_page ’
map.connect ‘’, :controller => “admin_pages”, :action=>“edit_pages”
map.connect ‘:controller/service.wsdl’, :action => ‘wsdl’
map.connect ‘:controller/:action/:id’

Has anyone else done something like this yet? I think the biggest
to this is doing some new hacks on the ActionController::Routing::Routes
add domain wildcards. So those who are doing, can
automatically route it to the specific controller and action.

I will be embarking on this sooner or later, but would be nice to see
else has done what.


 Nathaniel S. H. Brown                 

I’ve been thinking about this myself, but I haven’t done anything yet.
Actually, I played with it a little today, but nothing really
productive come of it.

My reason for doing so is to remove the need to add anything to
config/routes.rb, but also somehow allowing you to overwrite the
engine defaults if you want, or not having them at all. Seems a bit


On 3/10/06, Nathaniel S. H. Brown [email protected] wrote:

Has anyone else done something like this yet? I think the biggest advantage
Nathaniel S. H. Brown

engine-developers mailing list
[email protected]

Jeff L.

This forum is not affiliated to the Ruby language, Ruby on Rails framework, nor any Ruby applications discussed here.

| Privacy Policy | Terms of Service | Remote Ruby Jobs