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 -0000, [EMAIL PROTECTED]
<[EMAIL PROTECTED]> wrote:
> 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: CF-Talk
> > Subject: Re: CFCs and paths...I'm having a couple of problems...
> >
> > 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,"/",".")#.pathtocfc
> > s.inmy.app")
> > />
> >
> > I usually don't store my cfcs in a mapped CFC directory as this causes
> > me pain keeping track of them in CVS.
> >
> > Doug
> >
> >
> > On Tue, 15 Mar 2005 06:26:07 -0500, Calvin Ward <[EMAIL PROTECTED]> wrote:
> > > 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 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 seem like more work, but it pays you back
> > > later.
> > >
> > > On Mon, 14 Mar 2005 16:24:54 -0500, Bosky, Dave <[EMAIL PROTECTED]>
> > > wrote:
> > > > 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 Small [mailto:[EMAIL PROTECTED]
> > > > Sent: Monday, March 14, 2005 4:19 PM
> > > > To: CF-Talk
> > > > Subject: Re: CFCs and paths...I'm having a couple of problems...
> > > >
> > > > > 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 "search and replace" should be pretty
> > simple.
> > > >
> > > > Yeah, I've got nothing dynamic. So you're saying I should ask my ISP
> > for a
> > > > mapping? Think they'll do that? Is that a normal thing for ISPs to
> > offer?
> > > > This is just a little local telco, and it's a little pro bono site, so
> > I'm
> > > > wondering if asking for a mapping on their end would be a pain,
> > because
> > > > honestly, at this point, I don't care if it's a pain, I just want it
> > to
> > > > work.
> > > >
> > > >
> > >
> > >
> >
> >
> 
> 

~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~|
Find out how CFTicket can increase your company's customer support 
efficiency by 100%
http://www.houseoffusion.com/banners/view.cfm?bannerid=49

Message: http://www.houseoffusion.com/lists.cfm/link=i:4:198808
Archives: http://www.houseoffusion.com/cf_lists/threads.cfm/4
Subscription: http://www.houseoffusion.com/lists.cfm/link=s:4
Unsubscribe: 
http://www.houseoffusion.com/cf_lists/unsubscribe.cfm?user=11502.10531.4
Donations & Support: http://www.houseoffusion.com/tiny.cfm/54

Reply via email to