Oh, I see. I guess that’s even a little different. It’s not that you want different portions of your app to get different versions of object, you want the existence of a module to override all instances of it. Kind of like a module you can drop in that would modify the behavior of a core object for the entire app.
I’ll be honest, I’ve never tried that before. Luis may have some amazingly obvious way to do that but I’m not sure. Assuming the module mappings are processed after the root app’s mappings, can you access the actual mapping from the binder and modify to point to a different path? What happens if you just declare a mapping of the same ID in the module? Does that override, or just cause errors. I’m also trying to remember right now if modules actually use the same injector as the parent app, or if they use a child injector with it’s own binder of mappings.
Thanks!
~Brad
ColdBox Platform Evangelist
Ortus Solutions, Corp
E-mail: brad@coldbox.org
ColdBox Platform: http://www.coldbox.org
Blog: http://www.codersrevolution.com
