One other gotcha worth pointing out (that's not specific to CF really but may burn you if you're not aware of it) is if you run the Web Server connector wizard. This is offered by default during installation to allow you to connect your web server to JRun. Basically, it allows you to use URLs that don't require you to specify the JRun port, among other benefits.
But what's not obvious is that after doing this, you may have conflicts between the mappings for built-in JRun applications and any existing web server mappings or directory names of the same name. For instance, if you have a directory in your webroot called "demo" in which you have various CF templates, once JRun is installed and web server connector is run, you'll find that you can no longer run those templates. JRun will have caused the "/demo" mapping to point to its "demo" app. I had this problem and had to rename my demo directory to CFDemo. It wasn't a big deal, but it was curious until I figured it out. The same would go for /invoice and just plain /, which are also mapped to applications in JRun. /charlie -----Original Message----- From: Michael Wilson [mailto:[EMAIL PROTECTED]] Sent: Tuesday, November 20, 2001 3:57 PM To: JRun-Talk Subject: RE: Jrun and CF 5.0 Problems like that. I already have CF installed and am going to install Jrun 3.1 and wasn't sure if there was anything I should take care of before I did so. Mike > -----Original Message----- > From: charles arehart [mailto:[EMAIL PROTECTED]] > Back to your original question, Mike, were you thinking about > problems like this or something else? > > /charlie ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~ Structure your ColdFusion code with Fusebox. Get the official book at http://www.fusionauthority.com/bkinfo.cfm Archives: http://www.mail-archive.com/jrun-talk@houseoffusion.com/ Unsubscribe: http://www.houseoffusion.com/index.cfm?sidebar=lists
