Paul Roe said the following on 3/9/2006 4:16 PM:
> So your saying that the way that Mach-ii listeners use coldspring is
> incorrect, because I was under the understanding that most mach-ii'ers
> use the plugin that comes with this framwork.
No, the Mach-II plugin works just fine. However, listeners, filters,
plugins are all auto-wired. CS looks for setters (i.e. setXXX) and
tries to find the appropriate class in the bean factory.
> In my case I am essentially building a listener and I NEED access to
> the factory so that I can retrieve my DGO.
Listeners et all are all managed by Mach-II - hence the reason to supply
them with the bean factory.
> Since I am not using the coldspring factory in any different way than
> the mach-ii guys are I fail to see how you can say I'm trying to use
> in an incorrect manner.
Where ever CS puts it's beans - lives in a persistent scope
application.myBeans.getBean("theBeanINeed")
> This still doesn't negate the fact that in order to use coldspring in
> the same manner that mach-ii uses it I will have to manually pass the
> coldspring factory into my service rather than just specifying that
> the service requires a coldspring factory as an argument and allowing
> coldspring to pass itself into my service/listener.
Services and listeners are entirely different. Listeners are a custom
extension of the framework for your application in which they interact
with your model (sevices).
--
Peter J. Farrell :: Maestro Publishing
Member Team Mach-II :: Member Team Fusion
http://blog.maestropublishing.com
Create boilerplate beans and transfer objects for ColdFusion!
Fire up a cup of Rooibos!
http://rooibos.maestropublishing.com/
