Mike,
I've read everything you've said, in detail.
Yes, it took me a while to realize that when you said "shared hosting
environment" what you meant was "my development environment". I
already apologized for that oversight.
However, you're still going about this all wrong. That won't change
until you change the way you're going about this.
Your options haven't changed either:
Move reactor to the webroot and use /reactor as the root for all
reactor access. (good idea)
Put reactor anyone on your computer and make a /reactor mapping to
use for all reactor access. (acceptable idea)
Change Reactor's codebase to match your desired folder structure.
(horrible idea)
Use /site1, /site2, /site3 on development AND PRODUCTION so that the
paths on production and development are consistent. (best possible
solution)
Use vhosts on Apache to correctly mirror your development and
production environments. (excellent idea, but Apache can be hard to
get used to)
Yes, you have been rude, unkind, undiplomatic, accusatory, and even
insulting. And yet some of us are still trying to be helpful. I'm
sorry that you feel it necessary to bite the hand that types helpful
emails to you. Going off on Reactor, "people who write software for
CF", and anyone other than the person who's causing the problem,
isn't helpful.
And, finally, though this has been explained 10,000 times on cf_talk,
cfcdev, and a dozen other lists, you can't use random paths for CFCs
unless you've used web-inf.cftags.component for all your
returntype="" and cfargument type="" attribute values (or "any" or
just the CFC's name). If you're going to specify a path to a CFC, it
has to be explicitly declared and then adhered to. CS, MG, Reactor,
and most other CFC utility libraries have opted for the first choice,
explicit paths. Therefore, while your #application.appRoot# idea
might work fine for your cfincludes, image tags, etc., IT DOES NOT
WORK FOR ANY OF THE ABOVE.
What you have is a hack, and one that can't cover your needs at this
time. Therefore I propose that you stop trying to use Reactor until
you change the way you're doing things (as several have now
suggested... either virtual hosts or subfolders off the webroot)
because what you're trying to do cannot be done and your proposals
for changing Reactor are both unnecessary and likely to cause
breakages on down the line.
You have a non-standard setup that I would not recommend to anyone...
you've painted yourself into a corner. It's not Reactor's fault. It
has nothing to do with being a shared-hosting developer. It has
absolutely nothing to do with IIS, CF, Apache, Reactor, or anything
else. You have a rig that can't support what you want it to and you
either have to change how you're handling things or stop trying to
get Reactor to work the way you want it.
End of line... I have to leave to go see family and won't be back
till later. I've said about everything that can be said here. I've
read, re-read, studied your messages to try and be as helpful as
possible.
If that's not enough, then so be it.
Best regards,
J
-- Reactor for ColdFusion Mailing List -- [email protected]
-- Archives at http://www.mail-archive.com/reactor%40doughughes.net/
