|
Revision 543, 0.8 kB
(checked in by scorfield, 1 year ago)
|
|
Overhaul of skeleton to provide both a traditional (XML fusebox/circuit file) and new (no-XML files) versions.
Note that the new no-XML skeleton depends on Application.cfc and will not run on systems that do not support that.
This is mostly to illustrate how to use Application.cfc instead of fusebox.appinit.cfm and fusebox.init.cfm.
|
| Line | |
|---|
| 1 | <!--- |
|---|
| 2 | fusebox.appinit.cfm is included by the framework when the application is |
|---|
| 3 | started, i.e., on the very first request (in production mode) or whenever |
|---|
| 4 | the framework is reloaded, either with development-full-load mode or when |
|---|
| 5 | fusebox.load=true or fusebox.loadclean=true is specified. |
|---|
| 6 | It is included within a cfsilent tag so it cannot generate output. It is |
|---|
| 7 | intended to be for per-application initialization that can not easily be |
|---|
| 8 | done in the appinit global fuseaction. |
|---|
| 9 | It is included inside a conditional lock, ensuring that only one request |
|---|
| 10 | can execute this file. |
|---|
| 11 | |
|---|
| 12 | For example, if you are sharing application variables between a Fusebox |
|---|
| 13 | application and a non-Fusebox application, you can initialize them here |
|---|
| 14 | and then cfinclude this file into your non-Fusebox application. |
|---|
| 15 | ---> |
|---|
