Hey Kurt, Do you have "application." references in your components to find the factory in the application scope or do you pass them in as a property or constructor arg? Just curious.
Thanks, Pat On Sat, Dec 20, 2008 at 12:53 PM, Kurt Wiersma <kwier...@gmail.com> wrote: > > The caching and logging features can be accessed by your service layer > by using ColdSpring and the Utility connector. > > > http://greatbiztoolsllc-trac.cvsdude.com/mach-ii/wiki/FAQUsingUtilityConnector > > I have several apps like you are talking about with a shared set of > services across them. I use ColdSpring's parent bean factory support > to create a top level bean factory in my application.cfc which I store > in the app scope and then pull as the parent bean factory in my Mach > II apps. > > --Kurt > > On Sat, Dec 20, 2008 at 4:27 AM, Brian H. <bhen...@gmail.com> wrote: > > > > I am developing an application that includes a web-component (driven > > by mach-ii), and a flex component (driven by flex, and accessing my > > services through a Remote Proxy). > > > > I was in the middle of integrating coldspring into my mach-ii app > > using the property CFC provided, but it occurred to me that that this > > approach makes coldspring driven by mach-ii, when mach-ii in this case > > is not the CORE of the application. Since I have a remote facade on > > top of my service layer for servicing flex, requests could conceivably > > come in even when mach-ii was not even initialized. > > > > The same can be said about the use of mach-ii logging and caching. I > > see no problem when one is building a web app where all requests flow > > through mach-ii, but I start scratching my head during design when I > > look at my application as having multiple portals built on top of a > > service layer. In that view, mach-ii is only one of those portals. > > Web services, flex, WAP, etc all would be interacting through proxy > > objects outside of mach-ii. Building a application wide logging > > service through mach-ii then seems a bit inappropriate. Unless I > > treat the service as independent of mach-ii with it's own loader. > > > > In my case, should I forgo the coldspring property method and simply > > instance the coldspring factory in my app scope and use that object > > both from within mach-ii, and my flex proxy so that I have a single > > factory for the entire system? I would like to use the dependency > > injection features of coldspring to set up my listeners though, so > > should I opt for the property? What about my other portals? They > > would end up using their unique coldspring factory, meaning that the > > singleton aspect of my service objects might be broken since a single > > service object (UserService.cfc) would be instanced once for mach-ii, > > and once for the other portals? I see that the property has the > > "placeFactoryInApplicationScope" parameter, which I THINK would allow > > mach-ii to initialize the application wide factory, which my non-mach- > > ii apps could then use. Again though, mach-ii would have had to > > initialize before this factory is available, meaning I would have to > > treat my mach-ii app (which is essentially only concerned with the > > "web" portion of the app) as CORE to the system. > > > > So I am a bit confused here. Any advice would be greatly appreciated! > > > > Cheers! > > > > -Brian > > > > > > > > > > > --~--~---------~--~----~------------~-------~--~----~ 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: https://greatbiztoolsllc-svn.cvsdude.com/mach-ii/ Wiki / Documentation / Tickets: http://greatbiztoolsllc-trac.cvsdude.com/mach-ii/ -~----------~----~----~----~------~----~------~--~---
