How do the physical paths map to the website?
For example, does C:\Inetpub\wwwroot\MySite in your dev environment map to
www.something.ext\MySite in dev?
How does it look in production?
I wouldn't be surprised if a hosting organization would not want to manage
mappings for each site/client.
-
I hadn't tried the dynamic paths before... I wonder if this limitation is
documented anywhere?
- Calvin
-Original Message-
From: Paul Kenney [mailto:[EMAIL PROTECTED]
Sent: Monday, March 14, 2005 4:37 PM
To: CF-Talk
Subject: Re: CFCs and paths...I'm having a couple of problems...
The
I never noticed any issues with type checking when using dynamic paths
to my cfcs.
using the below gives me no issues
I sometimes set an application scoped var application.rootdir and use
something like
cfset toolsobj =
CreateObject(Component,#Replace(application.AppRoot,/,.)#.pathtocfcs.inmy.app)
Can anyone confirm if there are issues with Douglas' solution?
- Calvin
-Original Message-
From: Douglas Knudsen [mailto:[EMAIL PROTECTED]
Sent: Tuesday, March 15, 2005 8:46 AM
To: CF-Talk
Subject: Re: CFCs and paths...I'm having a couple of problems...
I never noticed any issues with
Doug
If you have a cfc which expects a cfc of a particular type e.g.
cfargument name=somecfc type=mypackage.somesubpackage.somecfc /
How do you handle it with dynamic paths?
KOla
-Original Message-
From: Douglas Knudsen [mailto:[EMAIL PROTECTED]
Sent: 15 March 2005 13:46
To:
Kola nailed the issue. Yeah, that woud be a show stopper. Currently,
I don't do this so much, so I never encountered it.
good cactch
Doug
On Tue, 15 Mar 2005 13:55:35 -, [EMAIL PROTECTED]
[EMAIL PROTECTED] wrote:
Doug
If you have a cfc which expects a cfc of a particular type e.g.
How do the physical paths map to the website?
For example, does C:\Inetpub\wwwroot\MySite in your dev environment map to
www.something.ext\MySite in dev?
Yes, exactly that.
How does it look in production?
Do you mean, how do the paths differ on the production machine? I believe
that the
Effectively you can't use variables in the type therefore they are less
useful in the component path?
-Original Message-
From: Douglas Knudsen [mailto:[EMAIL PROTECTED]
Sent: Tuesday, March 15, 2005 9:28 AM
To: CF-Talk
Subject: Re: CFCs and paths...I'm having a couple of problems...
paths to cfcs have to be absolute wite createObject() A pita for site
portability, eh? There are ways around this. You could create a CF
mapping called com to C:\Inetpub\wwwroot\com\. Then place your CFCs
in there in teh 'Java way'
C:\Inetpub\wwwroot\com\domainname\app1\mycfc.cfc
Then all
paths to cfcs have to be absolute wite createObject() A pita for site
portability, eh? There are ways around this. You could create a CF
mapping called com to C:\Inetpub\wwwroot\com\. Then place your CFCs
in there in teh 'Java way'
C:\Inetpub\wwwroot\com\domainname\app1\mycfc.cfc
Then
Just create the mapping on both your local and live sites. Use
hardcoded fully qualified paths if you can... try to avoid dynamic
path names when refering to the names of CFCs. It makes things easier
to understand when you look at it later, and if you have to change the
names at some point the
Just create the mapping on both your local and live sites. Use
hardcoded fully qualified paths if you can... try to avoid dynamic
path names when refering to the names of CFCs. It makes things easier
to understand when you look at it later, and if you have to change the
names at some point
Define in application.cfm file. You only have to look and change in a single
location. If at some point the location changes you don't need to search
and replace you know exactly where to look.
Also what's up with little local telco's? I think they rule!
-Original Message-
From: Jeff
A single mapping should be a one time thing, so it *shouldn't* be a
big deal for them.
On Mon, 14 Mar 2005 16:19:28 -0500, Jeff Small [EMAIL PROTECTED] wrote:
Just create the mapping on both your local and live sites. Use
hardcoded fully qualified paths if you can... try to avoid dynamic
I don't think they should have a problem with it. It's a simple thing
for them to do and if they're offering CF hosting, that's a simple
support issue that doesn't open any vulnerabilities on their server so
it shouldn't be a problem.
John Burns
Certified Advanced ColdFusion MX Developer
Wyle
OT
And HTC is the largest telephone cooperative in the US. Not just some
little local telco. :-)
/OT
- Matt Small
-Original Message-
From: Bosky, Dave [mailto:[EMAIL PROTECTED]
Sent: Monday, March 14, 2005 4:25 PM
To: CF-Talk
Subject: RE: CFCs and paths...I'm having a couple of
The issue with dynamic paths is that you can't do any type-checking at
all in the cffunction, cfargument, and cfproperty tags. For me,
this is too important since it saves a lot of time debugging. It also
makes the structure of component files clearer since I am always
having to use it. It may
OT
And HTC is the largest telephone cooperative in the US. Not just some
little local telco. :-)
/OT
- Matt Small
Well, you-know-who is lurking, so I figured I'd take a couple digs...make
sure he's paying attention...heh.
- Jeff Small (not related to Matt...seriously)
It's no problem for a hosting company that can open the
CFAdministrator. I set up a mapping for all the sites on my system as
a matter of routine when they sign up. I can set up other mappings
too if they want, but I set up a mapping to the root of their site,
with their domainname as the name
Add the base directory for your components as a 'Custom Tag Path' in
the CF Administrator. It also functions as a component path and will
be searched when you create a CFC. Also, unless your CFC is a
webservice, its best practice not to store it above the webroot.
-Adam
On Mon, 14 Mar 2005
20 matches
Mail list logo
