Hi Tim, Engines don't monkey patch classes, they override them. So, for example, if you bundle a User model in your Engine, it will replace (not enhance/extend/patch) the User model in the hosting application.
So you should never include an ApplicationController in your engine (well, I can't think of a use case where it would make sense, really). Also, it might be a good idea to use simplicity where possible. The engine API is there to bundle a mini-app inside of another app., not really to group utility methods. If there are methods you want to reuse in your controllers across projects, start by putting them into a module and include them on the controller (or make a nice DSL on the controller which can reference some of your behaviours). Hope this helps. I haven't really gone into your thread in depth as its Sunday, but the point I made above leapt out at me. Cheers, Nicholas -- You received this message because you are subscribed to the Google Groups "Ruby or Rails Oceania" group. To view this discussion on the web visit https://groups.google.com/d/msg/rails-oceania/-/J_odCSgjOdgJ. To post to this group, send email to [email protected]. To unsubscribe from this group, send email to [email protected]. For more options, visit this group at http://groups.google.com/group/rails-oceania?hl=en.
