Barry, I use cfinvoke if I have to pass a lot of variables because I find it
easier to read - or if I'm not passing all the possible variables, like if I
need to send just the first, third and fourth optional variables.
Example:
<cfinvoke component="theCFC" method="theMethod" returnvariable="theReturn">
<cfinvokeargument name="variable1" value="value1">
<cfinvokeargument name="variable3" value="value2">
<cfinvokeargument name="variable4" value="value3">
</cfinvoke>
Looks cleaner to me than:
<cfset theReturn=theCFC.theMethod(
variable1=value1,
variable3=value2,
variable4=value3)
Cheers,
Baz
-----Original Message-----
From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] On Behalf
Of Barry Beattie
Sent: Thursday, August 25, 2005 8:44 AM
To: [email protected]
Subject: Re: [CFCDev] Working with CFC's in a development version of a live
site
we have a config file that is read and used to tell us where the path
is (for us it's a server variable). Added to this is a ColdFusion path
that points to the folders' name. they both help. We have to do this
because theapp is going out to 150+ sites and they can call the folder
anything....
<cfset kernal = createObject("component", "#server.appPath#.tass.kernal") />
etc...
just a side question. Is there a reason why you're using cfinvoke?
curious, nothing more...
barry.b
On 8/25/05, Stephen Adams <[EMAIL PROTECTED]> wrote:
> Hi,
>
> I have a live site and a development site, which I use to test and build
any
> fixes for the live site. Both of them are on the same server. Now I'm
using
> components with the full address when I'm invoking them for example:
>
> <cfinvoke component="MyApp.cfc.MyComponent">
>
> But when I'm in the development version I have to change the invoke
> statement to:
>
> <cfinvoke component="MyDevApp.cfc.MyComponent">
>
> Is there any better way to have the two versions running on the same
server,
> using different sets of components, so I don't have to change all the
> cfinvoke calls?
>
> Thanks
>
> Stephen
> ----------------------------------------------------------
> You are subscribed to cfcdev. To unsubscribe, send an email to
> [email protected] with the words 'unsubscribe cfcdev' as the subject of
the
> email.
>
> CFCDev is run by CFCZone (www.cfczone.org) and supported by CFXHosting
> (www.cfxhosting.com).
>
> CFCDev is supported by New Atlanta, makers of BlueDragon
> http://www.newatlanta.com/products/bluedragon/index.cfm
>
> An archive of the CFCDev list is available at
> www.mail-archive.com/[email protected]
----------------------------------------------------------
You are subscribed to cfcdev. To unsubscribe, send an email to
[email protected] with the words 'unsubscribe cfcdev' as the subject of the
email.
CFCDev is run by CFCZone (www.cfczone.org) and supported by CFXHosting
(www.cfxhosting.com).
CFCDev is supported by New Atlanta, makers of BlueDragon
http://www.newatlanta.com/products/bluedragon/index.cfm
An archive of the CFCDev list is available at
www.mail-archive.com/[email protected]
----------------------------------------------------------
You are subscribed to cfcdev. To unsubscribe, send an email to
[email protected] with the words 'unsubscribe cfcdev' as the subject of the
email.
CFCDev is run by CFCZone (www.cfczone.org) and supported by CFXHosting
(www.cfxhosting.com).
CFCDev is supported by New Atlanta, makers of BlueDragon
http://www.newatlanta.com/products/bluedragon/index.cfm
An archive of the CFCDev list is available at
www.mail-archive.com/[email protected]
