# Edge Rails Apps Consuming 1.2 Rails Resources

**URL:** <https://www.ruby-forum.com/t/edge-rails-apps-consuming-1-2-rails-resources/109995>\
**Category:** Rails\
**Created:** [July 21, 2007, 12:31am UTC](https://www.ruby-forum.com/t/edge-rails-apps-consuming-1-2-rails-resources/109995 "2007-07-21T00:31:08Z")\
**Posts on this page:** 2\
**Page:** 1

<div class="post-metadata">

**Author:** ![misleb](https://www.ruby-forum.com/letter_avatar_proxy/v4/letter/m/e5b9ba/32.png) [@misleb](https://www.ruby-forum.com/u/misleb)\
**Post date:** [July 21, 2007, 12:31am UTC](https://www.ruby-forum.com/t/edge-rails-apps-consuming-1-2-rails-resources/109995/1 "2007-07-21T00:31:08Z")

</div>

Hi, I’m currently starting a new Rails app using Edge so I can utilize  
the Active Resources client. The app I am consuming resources from is a  
production 1.2.3 app (I can’t easily go Edge with it). The problem I’m  
having is that Edge has changed the Resources URL structure. In my  
production app, the URL for a custom action would be  
/users.xml;authenticate. In Edge is is something like  
/users/authenticate.xml.

s there any way to easily make them compatible or am I just SOL by this  
query string change until I can update the production app to Edge Rails?

I suppose I could simply construct my own query strings in the client,  
but that kinda takes the fun out of Active Resources.

-matthew

---

<div class="post-metadata">

**Author:** ![misleb](https://www.ruby-forum.com/letter_avatar_proxy/v4/letter/m/e5b9ba/32.png) [@misleb](https://www.ruby-forum.com/u/misleb)\
**Post date:** [July 21, 2007, 2:51pm UTC](https://www.ruby-forum.com/t/edge-rails-apps-consuming-1-2-rails-resources/109995/2 "2007-07-21T14:51:26Z")

</div>

I think that your best/only option is to map those custom actions  
using specific named routes:

map.resources :users, :collection =\> {:authenticate =\> :get}  
map.connect ‘users/authenticate.xml’, :controller =\> ‘users’, :action  
=\> ‘authenticate’, :format =\> ‘xml’

bye  
Luca

2007/7/21, Matthew I. [removed\_email\_address@domain.invalid](mailto:removed_email_address@domain.invalid):
