Get out the vote!
No, I'm not talking about the current Presidential election. I vow to keep this blog on topic.
I'm talking about Macromedia Bug #49546. Because of the fact the EXTENDS attribute of CFCOMPONENT cannot accept dynamic values, application frameworks such as Mach-II are forced to use hard coded component paths. This makes it very difficult to have multiple copies/versions of an application on a single(shared) server.
Macromedia Bug #49546 is a feature request to allow custom tag paths per application. Perhaps it could be implemented like <cfapplication customTagDirectory="d:\www\mysite\myCustomTags,d:\machii_1_0_10">
This would be a great enhancement for Mach-II apps. So, if you have access to the Macromedia beta program, you should have access to the bug tracker and you can cast your vote. If not, leave a comment here and we'll see if we get someone to submit a vote for you (you need to provide your name and email).
I'm talking about Macromedia Bug #49546. Because of the fact the EXTENDS attribute of CFCOMPONENT cannot accept dynamic values, application frameworks such as Mach-II are forced to use hard coded component paths. This makes it very difficult to have multiple copies/versions of an application on a single(shared) server.
Macromedia Bug #49546 is a feature request to allow custom tag paths per application. Perhaps it could be implemented like <cfapplication customTagDirectory="d:\www\mysite\myCustomTags,d:\machii_1_0_10">
This would be a great enhancement for Mach-II apps. So, if you have access to the Macromedia beta program, you should have access to the bug tracker and you can cast your vote. If not, leave a comment here and we'll see if we get someone to submit a vote for you (you need to provide your name and email).
2 Comments:
The cfimport tag has the same issue. This is bug 54075.
I need to install multiple copies of the Mach-ii framework within one JRun/ColdFuion Instance. I would like to see this feature, or one like it implemented with CFMX. If not set in cfapplication, then allow the sysadmin to restrict an Application to certain CustomTagPathes. This way, AppA would not see and call cfc's located in AppB.
Post a Comment
<< Home