>From the wiki...
----------------------------
Because Engines takes care of some of the load path, Ruby itself will
search for these files in order, and load the very first one it finds.
The paths this search will check are, in order:
* your app/models directory
* your lib directory
* the app/models directories in each engine, in active order
* the lib directories (and subdirectories) of each engine, in active
order.
----------------------------
Why is it that models act like this? I would expect that you could place
a model in your app/models directory and override/add methods (just like
controllers).
Technical limitations? Design flaw?
Curious...thanks.
--
Posted via http://www.ruby-forum.com/.
_______________________________________________
engine-developers mailing list
[EMAIL PROTECTED]
http://lists.rails-engines.org/listinfo.cgi/engine-developers-rails-engines.org
