You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
It would be helpful if the framework could check the parent ColdSpring? config for a service that is called via the call-method command if a module-specific ColdSpring? config file doesn't exist.
If you are creating a module that has no ColdSpring?-managed objects of its own, but do want to use ColdSpring?-managed objects in the parent application, you still have to set up a basic ColdSpring? Mach-II property in your module, and point it to an (essentially) empty ColdSpring? config file. If the framework could check for the service referenced in the call-method command in the parent app, then there would be no need for this.
hanged 18 months ago by peterjfarrell
Brian, I hope you don't mind but I adapted your blog post into the wiki to explain the problem on the call-method page.
The text was updated successfully, but these errors were encountered:
(Moved from http://trac.mach-ii.com/machii/ticket/694)
Please see
http://www.iterateme.com/blog/index.cfm/2010/4/16/MachII-Modules-Dont-Automagically-Inherit-ColdSpring-Configuration#comments
It would be helpful if the framework could check the parent ColdSpring? config for a service that is called via the call-method command if a module-specific ColdSpring? config file doesn't exist.
If you are creating a module that has no ColdSpring?-managed objects of its own, but do want to use ColdSpring?-managed objects in the parent application, you still have to set up a basic ColdSpring? Mach-II property in your module, and point it to an (essentially) empty ColdSpring? config file. If the framework could check for the service referenced in the call-method command in the parent app, then there would be no need for this.
hanged 18 months ago by peterjfarrell
Brian, I hope you don't mind but I adapted your blog post into the wiki to explain the problem on the call-method page.
The text was updated successfully, but these errors were encountered: