http://greatbiztoolsllc.trac.cvsdude.com/mach-ii/wiki/UsingColdSpringWithMach-II#ParentChildBeanFactoriesConfigurationforUsewithModules
jarthel said the following on 09/16/2009 11:34 PM: > Thanks peter. :) > > what doco are you referring? maybe I was looking at the wrong one? > > thanks again :) > > On Sep 17, 1:18 pm, "Peter J. Farrell" <pe...@mach-ii.com> wrote: > >> You can have a base coldspring defined in your base Mach-II application >> and have your modules coldspring inherit from it. Your module must have >> a coldspring property defined *as well* -- even if those have an XML >> file with no beans in them (just a<beans></beans in file will suffice). >> It's pretty clearly stated in the doco. Add a coldspring property in >> your module even it points to an XML file that doesn't have any beans in >> it -- it's required for inheritance. >> >> jarthel said the following on 09/16/2009 11:02 PM: >> >> >>> This is "base" coldspringProperty.xml:http://www.pastebin.ca/1569227. >>> >>> As can be seen, I have defined 2 beans as mach-ii properties. And >>> these works fine when I use call-method on the applicationService >>> (i.e. 1 event on the base app uses call-method). >>> >>> In my base "app", I have defined a frontend module. Down the track, I >>> will be creating a new module called "backend". >>> >>> I tried to perform the same call-method that worked for the base, on >>> my frontend module. call-method cannot find applicationsService. >>> >>> some questions/things I've done: >>> 1. I thought a module inherits whatever is on the base? I came to this >>> thinking because I have not defined a separate coldspringProperty for >>> my frontend module and my listeners can access applicationsService. >>> >>> 2. I looked at the parent/child beans (http:// >>> greatbiztoolsllc.trac.cvsdude.com/mach-ii/wiki/UsingColdSpringWithMach- >>> II#ParentChildBeanFactoriesConfigurationforUsewithModules). >>> >>> I tried creating a new coldspringProperty-frontend.xml. But it seems >>> the configFile property is required. I have defined everything I want >>> in the base coldspringProperty.xml. I am hoping my frontend module can >>> use this instead. Also when I have a backend module, I'm hoping >>> frontend and backend can share the coldspring resources. >>> >>> 3. removed coldspringProperty.xml in the base and put these in the >>> module. would not work at all. getting exceptions due to a plugin >>> (sessionFacade). >>> >>> Can someone please explain? >>> >>> thank you >>> >>> jayel >>> > > > --~--~---------~--~----~------------~-------~--~----~ You received this message because you are subscribed to Mach-II for CFML list. To post to this group, send email to mach-ii-for-coldfusion@googlegroups.com To unsubscribe from this group, send email to mach-ii-for-coldfusion-unsubscr...@googlegroups.com For more options, visit this group at http://groups.google.com/group/mach-ii-for-coldfusion?hl=en SVN: http://greatbiztoolsllc.svn.cvsdude.com/mach-ii/ Wiki / Documentation / Tickets: http://greatbiztoolsllc.trac.cvsdude.com/mach-ii/ -~----------~----~----~----~------~----~------~--~---