With the runtime parse patch, we're getting much closer to running the
Rails 'generate' script. At this point it manages to require all the
frameworks in; that in itself is pretty big. It continues on in the
Rails initializer, executing Initializer#process.
Initialize#process sets up the load path, requires in all the
frameworks, loads your environment, and then starts initializing
subsystems.
The first subsystem initialized is the database. This, unfortunately
does not run right, for reasons unknown. It appears to get stuck in a
loop, and eventually runs out of memory. It appears to be during YAML
parsing the default database.yml file, but I haven't investigated
further.
However, if this is commented out... The next failure is further down,
in the routing subsystem. This actually blows up with an error I've
seen in a few other places, but haven't investigated yet:
config/../vendor/rails/actionpack/lib/action_controller/routing.rb:63:in
`new': super: no superclass method 'new' (NameError)
from
config/../vendor/rails/actionpack/lib/action_controller/routing.rb:63:in
`new'
from
config/../vendor/rails/actionpack/lib/action_controller/routing.rb:352:in
`initialize_components'
from
config/../vendor/rails/actionpack/lib/action_controller/routing.rb:286:in
`collect'
...
So there we are.
It definitely shows we're making some progress. How are things on the
other front, Tom?
--
Charles Oliver Nutter @ headius.blogspot.com
JRuby Developer @ jruby.sourceforge.net
Application Architect @ www.ventera.com
-------------------------------------------------------
This SF.net email is sponsored by: Splunk Inc. Do you grep through log files
for problems? Stop! Download the new AJAX search engine that makes
searching your log files as easy as surfing the web. DOWNLOAD SPLUNK!
http://sel.as-us.falkag.net/sel?cmd=lnk&kid3432&bid#0486&dat1642
_______________________________________________
Jruby-devel mailing list
[email protected]
https://lists.sourceforge.net/lists/listinfo/jruby-devel
