I performed a test on my local machine and hacked the core pretty successfully. I was able to replace "reactor." With "applicationname.reactor." without any ill effects. Then I deployed reactor within my application.
I have some more tests to do and am looking for a solution that doesn't involve hacking the core. I'll summarize my work later and post to the list with my questions soon. But hacking the core was easy and successful. ----------------------------------- Gerry Gurevich Application Development NIEHS ITSS Contractor Lockheed Martin Information Technology 919-361-5444 ext 311 -----Original Message----- From: Terry L Schmitt [mailto:[EMAIL PROTECTED] Sent: Friday, October 13, 2006 1:52 PM To: [email protected] Subject: [Reactor for CF] Shared host mappings? Sanity check This is a multi-part message in MIME format. --=_alternative Content-Type: text/plain; charset="US-ASCII" Hi All, This is my first post to the list. I've been using Reactor moderately with some of my work related projects and rather enjoy it. I have now developed an app (using Reactor) that is to be hosted on a shared server. Now is where I kick myself in the butt for not doing better research before hand! The server that I'm using, of course, already has a /reactor mapping. Not good. I've read some of the posts on this list regarding this subject and I think the conclusion is that I'm pretty well hosed. I've exchanged emails with the hosting company and the reply is "Again, I am sorry, but the server mapping is a first come, first serve bases..." This is in reply to my requesting that they remove that mapping on the server and prevent it from being created again. So before I throw in the towel and remove Reactor from the app, does anyone have any last ideas? The mapping takes precedence, so I can't really see anyway around this other then hacking up Reactor. Terry Schmitt -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- Reactor for ColdFusion Mailing List [email protected] Archives at: http://www.mail-archive.com/reactor%40doughughes.net/ -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- --=_alternative Content-Type: text/html; charset="US-ASCII" <br><font size=2 face="sans-serif">Hi All,</font> <br><font size=2 face="sans-serif">This is my first post to the list.</font> <br><font size=2 face="sans-serif">I've been using Reactor moderately with some of my work related projects and rather enjoy it.</font> <br><font size=2 face="sans-serif">I have now developed an app (using Reactor) that is to be hosted on a shared server. Now is where I kick myself in the butt for not doing better research before hand!</font> <br> <br><font size=2 face="sans-serif">The server that I'm using, of course, already has a /reactor mapping. Not good. I've read some of the posts on this list regarding this subject and I think the conclusion is that I'm pretty well hosed.</font> <br><font size=2 face="sans-serif">I've exchanged emails with the hosting company and the reply is "Again, I am sorry, but the server mapping is a first come, first serve bases..." This is in reply to my requesting that they remove that mapping on the server and prevent it from being created again.</font> <br> <br><font size=2 face="sans-serif">So before I throw in the towel and remove Reactor from the app, does anyone have any last ideas? The mapping takes precedence, so I can't really see anyway around this other then hacking up Reactor.</font> <br> <br><font size=2 face="sans-serif">Terry Schmitt<br> </font> <br />-- -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- --<br />Reactor for ColdFusion Mailing List<br />[email protected]<br />Archives at: http://www.mail-archive.com/reactor%40doughughes.net/<br />-- -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- --=_alternative-- -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- Reactor for ColdFusion Mailing List [email protected] Archives at: http://www.mail-archive.com/reactor%40doughughes.net/ -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- --
