Kevin, That's only an issue if the hosting provider has mapped / to some other folder. CF 6 and 6.1 came with a default mapping of / to either the webserver webroot or c:\cfusionmx7\wwwroot depending on how you installed.
If you have no / mapping in CFIDE, your CF root and your webserver's virtual directory are the same location. In the case you've laid out below, I'd suggest reactor exist in all 3 webroot folders if you're working against a shared server and, if you really know that it will work and know how these locations work, you could put them in a common location... just depends on what you're doing. Laterz, J On Thu, 27 Jul 2006 00:11:25 +0100 "Kevin Roche" <[EMAIL PROTECTED]> wrote: > Thanks Jared. > > I guess the problem on a shared server is that each site > will have its own > "root" and ColdFusion will have a different root. > > Sites: > c:\inetpub\wwwroot\siteA > c:\inetpub\wwwroot\siteB > c:\inetpub\wwwroot\siteC > > The CF root is elsewhere: > c:\inetpub\wwwroot > > So I guess that as far as the CFC is concerned it must be > in: > c:\inetpub\wwwroot\reactor > > So that it can be found with the CFC path of: > reactor.reactorFactory > > Thanks for clarifying this. > > The issue that worries me slightly is that every user on > a shared server > must upgrade at the same time, since they are sharing the > copy of reactor. > > Another thought is that since the directory that reactor > is putting its code > in is also shared. let hope nobody else use the same name > for their project > and tables as I do! After all 'Intranet' and 'Person' > aren't too common are > they? > > Kevin > > > -----Original Message----- > From: [EMAIL PROTECTED] > [mailto:[EMAIL PROTECTED] > Behalf Of Jared Rypka-Hauer > Sent: 26 July 2006 23:44 > To: [email protected] > Subject: Re: [Reactor for CF] HELP--not of type > reactor.reactorFactory > > > CF references CFC paths from the current webroot, the > current folder, custom tag paths, and mappings, so if you > have c:\inetpub\wwwroot\reactor, you should be fine > instantiating reactor.reactorFactory. If you put your > Reactor distro in c:\cfusionmx7\custom tags, you should > be > fine instantiating reactor.reactorFactory. > > If you have ApplicationA at > c:\inetpub\wwwroot\applicationA > and put reactor in the app folder at > c:\inetpub\wwwroot\applicationA\reactor and try to > instantiate reactor.reactorFactory from > /applicationA/index.cfm, it will find the reactorFactory > object but blow up trying to find everything else that's > supposed to be at /reactor. > > If you have a /Reactor mapping, you could put Reactor at > c:\inetpub\wwwroot\applicationA\reactor, since there are > dependencies on the path /reactor, (for returntype and > type > attributes in various tags) you're asking for trouble > because CF prefers a local path to a root path if one > exists and you'll get various errors depending on what's > going on. You could end up with a bunch of "Object X > tried > to return an object of type > applicationa.reactor.project.... when it should be > returning an object of type > reactor.project.yadda.DAO.etc" > errors instead of the correct objects. > > All in all, your best bet is to put reactor at > c:\inetpub\wwwroot\reactor and leave it there. Let the > Reactor files themselves and CF manage the various paths > you need to get to things. IF, however, you want to have > c:\inetpub\wwwroot\applicationA\reactor contain your > project files, that's fine since the project files are > generated with the right paths from the get-go, you'd put > /applicationa/reactor in the config file or your > coldspring > config under the "mapping" attribute (yes, this is > confusing... it's not a CF mapping, it's where you want > Reactor to store the generated, persistent versions of > the > files it creates... DAO, metadata, dictionary, gateway, > TO, > record and validator). > > I hope that provides more clarity than confusion... > > Laterz, > J > > On Wed, 26 Jul 2006 23:32:01 +0100 > "Kevin Roche" <[EMAIL PROTECTED]> wrote: > > I deleted the mapping to /reactor on my laptop which is > > running IIS on > > Windows 2000 Pro. It still works, as far as I can tell! > > So the mapping was > > not really needed. > > > > Will have to try it on a Windows 2000 server where IIS > > mappings are set for > > multiple hosts and see what that does. > > > > I will let you know. > > > > Kevin > > > > > -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- > -- -- -- -- -- -- - > - -- > Reactor for ColdFusion Mailing List > [email protected] > Archives at: > http://www.mail-archive.com/reactor%40doughughes.net/ > -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- > -- -- -- -- -- -- - > - -- > > > > > -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- > -- -- -- -- -- -- -- -- > Reactor for ColdFusion Mailing List > [email protected] > Archives at: > http://www.mail-archive.com/reactor%40doughughes.net/ > -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- > -- -- -- -- -- -- -- -- > -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- Reactor for ColdFusion Mailing List [email protected] Archives at: http://www.mail-archive.com/reactor%40doughughes.net/ -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- --
