Re: [cfaussie] Extending Application.cfc
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 cfaussie@googlegroups.com. To unsubscribe from this group, send email to cfaussie+unsubscr...@googlegroups.com. For more options, visit this group at http://groups.google.com/group/cfaussie?hl=en.
Re: [cfaussie] Extending Application.cfc
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 cfaussie@googlegroups.com. To unsubscribe from this group, send email to cfaussie+unsubscr...@googlegroups.com. 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 cfaussie@googlegroups.com. To unsubscribe from this group, send email to cfaussie+unsubscr...@googlegroups.com. For more options, visit this group at http://groups.google.com/group/cfaussie?hl=en.
Re: [cfaussie] Extending Application.cfc
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 b...@palcare.com.auwrote: 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 cfaussie@googlegroups.com. To unsubscribe from this group, send email to cfaussie+unsubscr...@googlegroups.com. 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 cfaussie@googlegroups.com. To unsubscribe from this group, send email to cfaussie+unsubscr...@googlegroups.com. For more options, visit this group at http://groups.google.com/group/cfaussie?hl=en. -- E: mark.man...@gmail.com 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 cfaussie@googlegroups.com. To unsubscribe from this group, send email to cfaussie+unsubscr...@googlegroups.com. For more options, visit this group at http://groups.google.com/group/cfaussie?hl=en.
Re: [cfaussie] Extending Application.cfc
On 16/03/2011 10:27, Gavin Beau Baumanis wrote: But I know we did it for some reason. I just can't remember what it was! At this point I could make a comment about comments, but I won't :-) -- 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 cfaussie@googlegroups.com. To unsubscribe from this group, send email to cfaussie+unsubscr...@googlegroups.com. For more options, visit this group at http://groups.google.com/group/cfaussie?hl=en.
Re: [cfaussie] Extending Application.cfc
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 b...@palcare.com.au 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 cfaussie@googlegroups.com. To unsubscribe from this group, send email to cfaussie+unsubscr...@googlegroups.com. 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 cfaussie@googlegroups.com. To unsubscribe from this group, send email to cfaussie+unsubscr...@googlegroups.com. For more options, visit this group at http://groups.google.com/group/cfaussie?hl=en. -- E: mark.man...@gmail.com 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 cfaussie@googlegroups.com. To unsubscribe from this group, send email to cfaussie+unsubscr...@googlegroups.com. 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 cfaussie@googlegroups.com. To unsubscribe from this group, send email to cfaussie+unsubscr...@googlegroups.com. For more options, visit this group at http://groups.google.com/group/cfaussie?hl=en.
Re: [cfaussie] Extending Application.cfc
Oddly : There are no comments. But if you were to look at the rest of the code - there are comments everywhere. I am actually a bit of a comments junkie...Possibly even too much. Here's the cheat sheet I sent when we had offshore developers helping us out. • Comment all code, • Include SVN keywords at the beginning of all documents, • Include a fusedoc for all documents, • Format SQL for increased readability, • Test ALL changes locally, • Test ALL changes on the Staging server, • Comment all code, • Follow at all times the Design Standards Document, • Complete the PalCare Statement of Works Document, • If ever in doubt, seek the advice of your development team members, • Comment all code. Pity I can't read my own instructions! On 16/03/2011, at 10:37 AM, Kym Kovan wrote: On 16/03/2011 10:27, Gavin Beau Baumanis wrote: But I know we did it for some reason. I just can't remember what it was! At this point I could make a comment about comments, but I won't :-) -- 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 cfaussie@googlegroups.com. To unsubscribe from this group, send email to cfaussie+unsubscr...@googlegroups.com. 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 cfaussie@googlegroups.com. To unsubscribe from this group, send email to cfaussie+unsubscr...@googlegroups.com. For more options, visit this group at http://groups.google.com/group/cfaussie?hl=en.
Re: [cfaussie] Extending Application.cfc
Hi Gavin, Around CF 6-7 there was a bug with this as a workaround - the Advanced CF7 course uses the same idea of Application.cfc extending a blank base class. I'm not sure when the workaround became unnecessary. Robin ROBIN HILLIARD Chief Technology Officer ro...@rocketboots.com.au RocketBoots Pty Ltd Level 11 189 Kent Street Sydney NSW 2001 Australia Phone +61 2 9323 2507 Facsimile +61 2 9323 2501 Mobile +61 418 414 341 www.rocketboots.com.au On 16/03/2011, at 9:57 AM, Gavin Beau Baumanis wrote: Let me start with; This might sound a little weird. We have extended Application.cfc which extends BaseApplication.cfc I am pretty sure that I have discussed it before, but a search of the group hasn't turned up anything. The reason for this post is - I am sure I did the extends for a real / valid reason - but can't for the life of me remember what for. There is nothing in the Application.cfc but for the extends BaseApplication attribute. -- You received this message because you are subscribed to the Google Groups cfaussie group. To post to this group, send email to cfaussie@googlegroups.com. To unsubscribe from this group, send email to cfaussie+unsubscr...@googlegroups.com. For more options, visit this group at http://groups.google.com/group/cfaussie?hl=en.
