|
Revision 663, 0.8 kB
(checked in by scorfield, 1 year ago)
|
|
Fixes #304 by tightening up skeleton app code for initialization and application naming. Also makes a
slight change to appinit to allow for the framework being initialized via a remote CFC call. It is not
an ideal change but it solves the basic problem.
|
| Line | |
|---|
| 1 | <cfcomponent extends="fusebox5.Application" output="false"> |
|---|
| 2 | <!--- |
|---|
| 3 | sample Application.cfc for ColdFusion MX 7 and later compatible systems |
|---|
| 4 | ---> |
|---|
| 5 | |
|---|
| 6 | <!--- set application name based on the directory path ---> |
|---|
| 7 | <cfset this.name = right(REReplace(getDirectoryFromPath(getCurrentTemplatePath()),'[^A-Za-z]','','all'),64) /> |
|---|
| 8 | |
|---|
| 9 | <!--- enable debugging ---> |
|---|
| 10 | <cfset FUSEBOX_PARAMETERS.debug = true /> |
|---|
| 11 | |
|---|
| 12 | <!--- force the directory in which we start to ensure CFC initialization works: ---> |
|---|
| 13 | <cfset FUSEBOX_CALLER_PATH = getDirectoryFromPath(getCurrentTemplatePath()) /> |
|---|
| 14 | |
|---|
| 15 | <!--- |
|---|
| 16 | if you define any onXxxYyy() handler methods, remember to start by calling |
|---|
| 17 | super.onXxxYyy(argumentCollection=arguments) |
|---|
| 18 | so that Fusebox's own methods are executed before yours |
|---|
| 19 | ---> |
|---|
| 20 | |
|---|
| 21 | </cfcomponent> |
|---|
