It uses a number of file naming conventions to encourage this separation: presentation files begin with dsp (display) or lay (layout), database access files begin with qry (query) and general business files begin with act (action). The query-string variable name 'fuseaction' can vary depending on configuration parameters, so not all applications using Fusebox need to use the action variable 'fuseaction'.ДЇusebox encourages, but does not enforce, separation of presentation logic from business logic. URLs within a Fusebox web application are usually of the form index.cfm?fuseaction=cname.fname where ' cname' is the name of a circuit and ' fname' is an XML-defined 'method' within that circuit known as a fuseaction. As such, Fusebox is considered an implementation of the front controller, a common design pattern. Each circuit in the application is further divided into small files called fuses that should perform simple tasks. The application is divided into a number of circuits (usually in sub-directories) which are intended to contain related functionality. In a Fusebox web application, all requests are routed through a single point (usually index.cfm for CFML) and processed by the Fusebox core files. The original concepts behind Fusebox were based on the household idiom of an electrical fusebox that controls a number of circuits, each one with its own fuse. The framework did not address creating and maintaining business logic such as database interaction or service layersД¬oncepts Fusebox, Circuits and Fuseactions The framework has been ported and used in ASP, JSP, Lasso, Perl/ CGI and PHP as well, though the CFML and PHP versions of Fusebox were the only versions to gain momentum.ДЇusebox dealt primarily with the effort of wiring together view states (pages) with controller actions (form submits, etc.) and the front-end of the business-logic tier. (Many people refer to Fusebox as a 'methodology', but in fact, it was a development framework. In addition to the framework itself, Fusebox became closely associated with a Web application development methodology developed by its proponents known as ' FLiP' (for Fusebox Lifecycle Process). Fusebox provided web application developers with a standardized, structured way of developing their applications using a relatively straightforward and easy to learn set of core files and encouraged conventions.

Icefaces 3.3 complete reference pdf