ColdSpring - Locating CFC's outside Web Root???

I am in the process of creating a template application, using the following frameworks:

  • Fusebox 5.1
  • ColdSping
  • Transfer
I have run into the following issue.

We have tried to only have files within the web root, which should be accessible directly within the browser.

[More]

Comments
Brian Kotek's Gravatar A generic factory like this begs the question, why are you even using ColdSpring? There's no advantage. No capability for dependency resolution. No AOP. No remote proxies. This is definitely a bad idea.

Is there a reason why you don't just define ColdFusion mappings so that your local, stage and produciton CFC paths are the same? Otherwise, having ANT replace the values in the config file is a valid option.
# Posted By Brian Kotek | 17/08/07 23:12
Daniel Lancelot's Gravatar @Brian:

Yeah - I had thought that it might be possible to use the depenency resolution etc. with the bean that is the result of calling the factory method? I can see though that it does feel like I'm negating a lot of the benefits of using CS.

Mappings can be (and are) identical between local and live. Staging however is often on the same server as live (we are talking multiple apps per server for most stuff here - no dedicated staging servers) - so mappings need to be different.

Im torn between using ANT - and moving the CFC's under the web root... (App specific mappings would be nice - but we're stuck on CF7 for the forseeable future...)
# Posted By Daniel Lancelot | 17/08/07 23:44
BlogCFC was created by Raymond Camden. This blog is running version 5.5.1, hosted by TalkWebSolutions.