On Thu, Dec 29, 2011 at 8:31 AM, David Mulder <[email protected]>wrote:
> In ACF you can set the following: > > test.cfc > <cfinclude template="#application.**comroot#somedir.somefile"> > > extendtest.cfc in same directory as test.cfc > <cfcomponent extends="test"> > </cfcomponent> > You're saying that *doesn't* work in OpenBD? What happens exactly? (Sorry, can't test right this minute.) > It's not without reason that one is using a high level language such as > coldfusion, one of those is that you don't want to go through the trouble > of building stuff. And these global definitions are used as they differ on > development vs staging vs production. > Well, it might be worth considering having your environments more consistent as well. In a lot of instances people have differing environments for no reason other than they haven't made the effort to make things more consistent. Particularly when it comes to where your components are located it seems odd to me that it'd be a necessity that these live in different places from environment to environment. Maybe that's just the way I do things but it avoids all these types of problems. > Correctly in the sense of "in line with ACF", thus allowing a cfc with an > cfinclude and without cfcomponent tags. Hope this clarifies it a bit. Where you lose me is why you need to do this without cfcomponent tags. Why does that matter? -- Matthew Woodward [email protected] http://blog.mattwoodward.com identi.ca / Twitter: @mpwoodward Please do not send me proprietary file formats such as Word, PowerPoint, etc. as attachments. http://www.gnu.org/philosophy/no-word-attachments.html -- online documentation: http://openbd.org/manual/ google+ hints/tips: https://plus.google.com/115990347459711259462 http://groups.google.com/group/openbd?hl=en
