HI Mark / Kym, I do realise that it is a bit of a stupid question / fishing exercise. I genuinely can't recall why we did it. I have done a bit of a google search, hoping to find my original discussion - or perhaps the content that I worked from when doing the change... But haven't found anything that springs to mind.
Something about mappings seems familiar - but since we're not extending BaseApplication.cfc anywhere else in the application - that seems odd... The only thing I can think of is that we had an issue originally, that extending the Application.cfc fixed - but we later re-factored the code out of the requirement to need the extends behaviour. *shrugs* - I really don't know. Not to worry - and thanks to you both for your replies. Gavin. On 16/03/2011, at 10:34 AM, Mark Mandel wrote: > You wanted to share common application settings across disparate directories > / web applications? > > Mark > > On Wed, Mar 16, 2011 at 10:27 AM, Gavin Beau Baumanis <[email protected]> > wrote: > Hi Kym, > > Thanks. > Weirdly, we don't put anything into Application.cfc. > This is it; > <cfcomponent name="Application" extends="BaseApplication"> > </cfcomponent> > > And we have BaseApplication.cfc and Application.cfc in the same directory. > (with no other Application.cfc s anywhere in the application) > > So it seems like a bit of a waste of time. > > But I know we did it for "some" reason. > I just can't remember what it was! > > > > On 16/03/2011, at 10:20 AM, Kym Kovan wrote: > > > On 16/03/2011 09:57, Gavin Beau Baumanis wrote: > > > >> So I thought I would ask for the normal use-cases that an Application.cfc > >> gets extended - in the hope I might be able to recall why we did it in the > >> first place. > >> (Of course I'll document on our internal Wiki - once I know!!) > > > > A good example might be an admin area of a site that needs some extra > > security bits on top of whatever functionality you have in App.cfc. You > > extend the app cfc and drop your extra code in. In olden times you might > > have used an include file for the common code. > > > > Of course you can also bump into the horrors of extending into different > > folders and have to use proxies, etc but that is another story :-) > > > > > > -- > > Yours, > > > > Kym Kovan > > mbcomms.net.au > > > > > > -- > > You received this message because you are subscribed to the Google Groups > > "cfaussie" group. > > To post to this group, send email to [email protected]. > > To unsubscribe from this group, send email to > > [email protected]. > > For more options, visit this group at > > http://groups.google.com/group/cfaussie?hl=en. > > -- > You received this message because you are subscribed to the Google Groups > "cfaussie" group. > To post to this group, send email to [email protected]. > To unsubscribe from this group, send email to > [email protected]. > For more options, visit this group at > http://groups.google.com/group/cfaussie?hl=en. > > > > > -- > E: [email protected] > T: http://www.twitter.com/neurotic > W: www.compoundtheory.com > > cf.Objective(ANZ) - Nov 17, 18 - Melbourne Australia > http://www.cfobjective.com.au > > Hands-on ColdFusion ORM Training > www.ColdFusionOrmTraining.com > > -- > You received this message because you are subscribed to the Google Groups > "cfaussie" group. > To post to this group, send email to [email protected]. > To unsubscribe from this group, send email to > [email protected]. > For more options, visit this group at > http://groups.google.com/group/cfaussie?hl=en. -- You received this message because you are subscribed to the Google Groups "cfaussie" group. To post to this group, send email to [email protected]. To unsubscribe from this group, send email to [email protected]. For more options, visit this group at http://groups.google.com/group/cfaussie?hl=en.
