In all our applications we have a global definitions file loaded into the application scope which defines constants containing paths to various locations in our application. Of course if we would be building a new application framework we could simply use dynamic mappings, but as I am right now porting an existing system that's quite out of the option. Now to the actual problem: ACF (and OBD as well) don't allow the extend attribute to be dynamic for a cfcomponent tag. In ACF this can be solved extremely simply (although ugly) by linking to a file in the same directory which contains a dynamic include, however in OBD this isn't possible as a .cfc is required to contain cfcomponent tags. Personally I don't really see a reason why the attribute would need to be "constant" in the first place, so if possible I would like to propose that that limitation is taken of in the first place? The last hour and half I have tried compiling openbd myself with cfCOMPONENT.java:156 commented out, but I simply couldn't get openbd to compile in the first place (I got stuck setting ant up correctly as I have never used ant before). Either way, if there is a real technical reason for the limitation than I would propose that at the very least a .cfc with an include could be handled "correctly" (in the same way as ACF does).

 David

--
online documentation: http://openbd.org/manual/
  google+ hints/tips: https://plus.google.com/115990347459711259462
    http://groups.google.com/group/openbd?hl=en

Reply via email to