Is it possible to have multiple MVC routes point to the same controller/view?

To fix this issue Solved. Sorry!
Problem: routes.businessregistration_businessregistration_en.defaults.locale = "de_DE"

wish helps you My I suggest that you create a new controller to handle this? The advantage is that you can map the route to this controller on any models you want the "remove association" on.
For example:

# RemoveController.rb
class RemoveController < ApplicationController
  def destroy
     # inplement the logic for deletion. You can use refection to implement 
     # this function only once for all the applied associations.    
  end
end

# routes.rb
resources :companies do
  resource :requests do
    resource :remove, :controller => :remove, :only => [:destroy]
  end
end

company_requests_remove DELETE /companies/:company_id/requests/remove(.:format)          remove#destroy

# routes.rb
resources :companies do
  resource :requests do
    resource :remove, :controller => :relationship, :only => [:destroy]
    resource :create, :controller => :relationship, :only => [:create]
  end
end

company_requests_remove DELETE /companies/:company_id/requests/remove(.:format)        relationship#destroy
company_requests_create POST   /companies/:company_id/requests/create(.:format)        relationship#create

should help you out Routes in MVC are compared in the order you add them. For your code sample, this means that all requests will be compared to the "HomeTest" route first, so any matches will follow that route. The "TestTest" route has the exact same format, which means that it will never be used because any matches will have already used the "HomeTest" route. If you want to get to get to a controller's actions without using the controller name, there must be something in the route to tell it which controller to use. This doesn't have to be the actual controller name - you can do this:

routes.MapRoute("TestTest", "keyWord/{action}/{id}", new { controller = "Test", action = "Test", id = UrlParameter.Optional });
routes.MapRoute("UsersTest", "otherKeyWord/{action}/{id}", new { controller = "Users", action = "Test", id = UrlParameter.Optional });

routes.MapRoute("TestTest", "test/key1/{id}", new { controller = "Test", action = "Test", id = UrlParameter.Optional });
routes.MapRoute("UsersTest", "test/key2/{id}", new { controller = "Users", action = "Test", id = UrlParameter.Optional });

this will help I'm currently in a situation where my Rails application has quite a few Rails Engines in it. To solve architecturally, we began using a module to namespace our models/views/controllers away from other Rails Engines that were in the app such as Devise, AlchemyCMS, and Spree. , Why not use scope instead of namespace:

 scope '/my_application' do
   get '/cart' => 'orders#edit'
 end

seems to work fine You have two identical routes that are both POST: post '/user_selections'
This part of a route must be unique.

 post '/user_selections', to: "userselections#select", as: :user_selection_category
 create '/user_selections', to: "userselections#create", as: :new_user_selections

 post '/user_selections/select', to: "userselections#select", as: :user_selection_category
 post '/user_selections', to: "userselections#create", as: :new_user_selections