Bookmark
Edit in Word
|
Fusebox
|
Alternatives to using fusebox.xmlAs of FuseNG 1.0 (Fusebox 5.5) fusebox.xml is not necessary any longer. The file can be entirely implicit (accepting default values for the parameters) or can mostly be replaced by extending FuseNG.Application in the project's Application.cfc. PurposeFuseNG.xml is the main configuration for FuseNG. This lets FuseNG know about the overall structure of your application and, at a high level, how you want your application to function. In No XML FuseNG this can be implicit with much of the information configured in Application.cfc. FUSEBOX_PARAMETERS takes precedence over paremeters set in the fusebox.xml file. For security purposes put .cfm on this file so it can not be accessed by HTTP requests. From Trac:Here is a very basic fusebox.xml file to refer to as we cover the XML elements: A FuseNG application has only one fusebox.xml file. It is located in the root directory of the application. In Fusebox version 4 the Fusebox core files were also located in the application root but in versions 4.1 and 5 they can be located anywhere under the ColdFusion root. This allowed one copy of the fusebox core to be shared by several applications. ::TODO:: The <fusebox> tag can declare XML namespaces that let you use custom attributes on classes and plugins. This file is the foundation for your entire application. This XML file consists of the root element, fusebox, and five primary sub-elements: A fusebox.dtd Document Type Definition (DTD) file is provided with the core files and also currently hosted on fusebox.org. Including it in your doctype definition on top of the fusebox.xml file will allow XML editors like Dreamweaver or Eclipse to provide autocompletion as well as validate any XML you've already written. Example:<?xml version="1.0" encoding="UTF-8"?> |
