The [beanFactoryPropertyName] parameter value is the name of the Mach-II property name that will hold a reference to the ColdSpring beanFactory. This parameter defaults to "coldspring.beanfactory.root" if not defined. The [configFile] paramater value holds the path of the ColdSpring configuration file. The path can be an relative, ColdFusion mapped or absolute path. If you are using a relative or mapped path, be sure to set the [configFilePathIsRelative] parameter to TRUE or the ColdSpring will not find your configuration file. The [configGilePathIsRelative] parameter value defines if the configure file is an relative (including ColdFusion mapped) or absolute path. If you are using a relative or mapped path, be sure to set the [configFilePathIsRelative] parameter to TRUE or the property will not find your configuration file. - TRUE (for relative or mapped configuration file paths) - FALSE (for absolute configuration file paths) The [resolveMachIIDependencies] parameter value indicates if the property to "automagically" wire Mach-II listeners/filters/plugins/properties. This parameter defaults to FALSE if not defined. - TRUE (resolves all Mach-II dependencies) - FALSE (does not resolve Mach-II dependencies) The [parentBeanFactoryScope] parameter values defines which scope to pull in a parent bean factory. This parameter defaults to 'false' if not defined and indicates that a parent bean factory does not need to be referenced. The [parentBeanFactoryKey] parameter values defines a key to pull in a parent bean factory from the scope specified in the [parentBeanFactoryKey] parameter. This parameter defaults to 'false' if not defined and indicates that a parent bean factory does not need to be referenced. The [placeFactoryInApplicationScope] parameter indicates whether or not to place the bean factory in the application scope. This parameter is used to for setting your bean factory for use as a parent. The key that used is driven from the value from of the [beanFactoryPropertyName] parameter. If the parent uses the same value for the beanFactoryPropertyName, the module name (e.g. "_account") is append to the end of the key to eliminate namespace conflicts in the application scope. This parameter defaults to 'false' if not defined and indicates that this bean factory should not be placed in the application scope. The [placeFactoryInServerScope] parameter indicates whether or not to place the bean factory in the server scope. This parameter is used to for setting your bean factory for use as a parent. The key that used is driven from the value from of the [beanFactoryPropertyName] parameter. If the parent uses the same value for the beanFactoryPropertyName, the module name (e.g. "_account") is append to the end of the key to eliminate namespace conflicts in the server scope. This parameter defaults to 'false' if not defined and indicates that this bean factory should not be placed in the server scope. The [autowireAttributeName] parameters indicates the name of the attribute to introspect for in cfcomponent tags when using the dynamic autowire getter/setter method generation feature of the Coldspring Property. Autowire method generation injection allows you to put a list of ColdSpring bean names in the autowire attribute (which default to 'depends') in cfcomponent tag of your listeners, filters, plugins and properties CFC in Mach-II. ColdSpring property will automatically generate and dynamically inject getters/setters for the listed bean names into your target cfc at runtime. This does not modify the contents of the cfc file, but injects dynamically while the cfc is in memory. This feature allows you to stop having to type out getters/setters for the service that you want ColdSpring to inject into your cfc. Example: ... additional code ... This will dynamically inject a getSomeService() and setSomeService() method into this listener. ColdSpring will then use the bean name and use setter injection to inject the bean into the listener. The [beansToMachIIProperties] parameter holds a struct of bean names and corresponding Mach-II property names. This parameter will inject the specified beans in the Mach-II property manager as the bean factory has been loaded. In the past, a seperate property has to be written to accomplish this task. This should be used for framework required "utility" objects that you want to be managed by ColdSpring such as UDF, i18n or session facade objects. Do not use this feature to inject your model objects into the Mach-II property manager. Parent/Child Bean Factories Configuration for Use with Modules: Base Mach-II Config File (i.e. Parent Factory) You must put the parent bean factory in the application (or server scope) in order for a module to inherit from a parent factory. This example put the parent factory into the application.serviceFactory variable. Account Module Config File (i.e. Child Factory): You are NOT required to put child factories into the application (or server scope) for modules to inherit froma a parent factory. However, in this example the account module puts this child factory into the application scope. Since the parent and module use the same beanFactoryPropertyName, an application scope namespace conflict would occur - so the Property appends the module name to the end. This factory would be located in application.serviceFactory_account variable. ---> ') /> ') /> ') /> ') />