Posted on September 13, 2007 at 7:21 PM in Fusebox
The other day Sean released a FB5.5 update to the Cat Club demo application, so I downloaded it to play around a bit with the new toy. I am truly excited about the option to eliminate XML from one's Fusebox applications.
IMPORTANT: The XML is still perfectly valid, and the FB5.5 release will *not* break older apps. As a matter of fact, I have several 5.1 applications that are now running on the 5.5 core, without a single keystroke change to the code.
When I unzipped and ran the Cat Club demo from the webroot, it performed flawlessly. And fast? Yes! Very. "So far so good," I thought, and then I went to putting together my own little demo app, utilizing the implicit circuit feature (no XML). That's when I stubbed my toe, fell down, and skinned up my knees.
I talked with Sean for a good while on my issue, and try as he might, he was unable to duplicate it on his machine. So, I thought I'd throw out this post and see if anyone else runs into the same issue.
Here's what I did: moved the application into a sub-directory of the webroot, and immediately received the following error message:
"Well, you dummy," I mused, "you need to reload the application! Oh, and be sure to parse all!"
Unfortunately, doing so resulted in no change in behavior whatsoever. It seems to me that the Fusebox core is not correctly setting the paths to the application root, and therefore, the paths to the controller / model / view directories are incorrect as well. Here is the controller path that I **think** is being set...
Why do I think that? Well, the sample app's name is "ggcc55", and a fuseaction of 'ggcc.home' is being requested - which is the 'ggcc' controller - and the error message indicates that FB is attempting to create a component with a path of 'ggcc55.controller.ggcc'.
So long as I have the files residing in the webroot (D:WebDev in my case) as so...
... the application loads without any troubles. Below is a screencap of this directory structure.
Once I move the application files to a lower directory, that's when my troubles arise. Here is the directory structure that I tried to use, below which is a screencap.
So, my question is, can anyone else duplicate this issue? Or is it just me? I can reliably reproduce the issue on all of my test servers, as well as my production servers.
By the way, I'm running Windoze XP Pro w/ IIS on my test server, and Windoze Server 2003 Standard Edition w/ IIS on my production servers.
- ColdBox (21) [RSS]
- ColdFusion (92) [RSS]
- Fusebox (3) [RSS]
- General (22) [RSS]
- jQuery (15) [RSS]
- Kalendar (1) [RSS]
- Linux (1) [RSS]
- Mura CMS (1) [RSS]
- Railo (1) [RSS]
- Rants (5) [RSS]
- Transfer (8) [RSS]
- Uni-Form Tag Library (36) [RSS]