[Rails-core] Re: application controller methods and routes (RC1)

2006-11-28 Thread Michael Koziarski
> > Ok, I can live with that, but this might be something that should be > made a little, ok, a lot more obvious in the upgrade path notes... on > the weblog, etc. Yeah, this is definitely worth mentioning in the upgrade guide. -- Cheers Koz --~--~-~--~~~---~--~---

[Rails-core] Re: application controller methods and routes (RC1)

2006-11-28 Thread Andrew Kaspick
Ok, I can live with that, but this might be something that should be made a little, ok, a lot more obvious in the upgrade path notes... on the weblog, etc. Since I've never seen/read anything that discourages calling methods on the ApplicationController, I'm sure I'm not the first to have done it

[Rails-core] Re: application controller methods and routes (RC1)

2006-11-28 Thread Tim Lucas
On 29/11/2006, at 9:46 AM, Michael Koziarski wrote: > >> no route found to match "/application/main_login" with >> {:method=>:get} >> >> I've found that all my application controller methods produce the >> same >> result. Has something been deprecated that I'm unaware of or am I >> missing s

[Rails-core] Re: application controller methods and routes (RC1)

2006-11-28 Thread Michael Koziarski
> no route found to match "/application/main_login" with {:method=>:get} > > I've found that all my application controller methods produce the same > result. Has something been deprecated that I'm unaware of or am I > missing something obvious (based on the info here) and just doing > something s

[Rails-core] application controller methods and routes (RC1)

2006-11-28 Thread Andrew Kaspick
Posting here as it applies to RC1, apologies if it should be in the main rails list. I'm trying RC1 out and have found that I can't call any methods from my application controller now. For example, I have a method called main_login in ApplicationController and when I attempt to access via url as

[Rails-core] Re: Rails support progress for JRuby

2006-11-28 Thread Thijs van der Vossen
On Nov 28, 2006, at 9:35 PM, Charles Oliver Nutter wrote: Just to be clear, ActiveRecord-JDBC already works with both Derby/JavaDB and HSQLDB, and I believe it also supports migrations. Mainly what we'd need is a simple way to run tests that depend on SQLite against something other than SQLite. I

[Rails-core] Re: Rails support progress for JRuby

2006-11-28 Thread Charles Oliver Nutter
Just to be clear, ActiveRecord-JDBC already works with both Derby/JavaDB and HSQLDB, and I believe it also supports migrations. Mainly what we'd need is a simple way to run tests that depend on SQLite against something other than SQLite. I just don't know how to make that happen without directly m

[Rails-core] Re: Rails support progress for JRuby

2006-11-28 Thread Rob Sanheim
On 11/28/06, Charles Oliver Nutter <[EMAIL PROTECTED]> wrote: [snip] > Note that the use of SQLite in many places in the test causes quite a > bit of trouble for JRuby since SQLite support on Java is minimal at > best. The ability to swap out SQLite for something equivalently simple > (DBI or JDBC

[Rails-core] Rails support progress for JRuby

2006-11-28 Thread Charles Oliver Nutter
FYI, I've been keeping an updated page of Rails test run results with JRuby at the following URL http://www.headius.com/jrubywiki/index.php/Rails_Support The bottom line is that ActionPack/ActiveSupport/ActionMailer are nearly 100%, ActiveRecord is probably 2/3 working (but the failures include