tracker issue : CF-3037145

select a category, or use search below
(searches all categories and all time range)
Title:

Bug 74757:(Watson Migration Closure)Read this thread for discussion

| View in Tracker

Status/Resolution/Reason: Closed/Deferred/

Reporter/Name(from Bugbase): John Farrar / John Farrar (sosensible)

Created: 12/29/2008

Components: Language, CustomTag

Versions: 9.0

Failure Type: Unspecified

Found In Build/Fixed In Build: 0000 /

Priority/Frequency: Normal / Unknown

Locale/System: English / Platforms All

Vote Count: 4

Problem:

Read this thread for discussion...
https://prerelease.adobe.com/project/forum/thread.html?cap=87529BDA13744B3DB718E841890B9240&forid={81302E9C-2163-4C37-9582-D9C14B236AE8}&topid={8B49307F-3533-4BD8-ACC5-16BFADC791EE}

Request to add import feature to Application.cfc. You will see that Sean and I talked it out and it 'seems' that we have an excellent solution for making that so the existing hard coded template by template version will continue to work and so the tag libary path prefix can be created at application level in a way that will not cause any conflict or compiler road blocks. (Note... as a developer not saying this is a couple minutes work, but it would VERY MUCH boost the benefit and use of Custom Tags.)

<myLib:myTag ...> without on page <CFImport> using Application declared libraries. (Also note that inside a server CFModule is not as easy to support in code, and using <cf_myTag...> we have had a couple of instances with customers on shared hosting finding conflicts with someone else's map conflicting with a map they added. We have found mapped libraries is the easiest to code, support and has the least conflicts.
Method:


Result:

----------------------------- Additional Watson Details -----------------------------

Watson Bug ID:	3037145

External Customer Info:
External Company:  
External Customer Name: John Farrar
External Customer Email: 0F46649A47B597BE992015A7
External Test Config: 12/29/2008

Attachments:

Comments:

This would be a nice feature. Although the 'Shared hosting' issue hasn't been an big one with my company. We prefix all libraries with domainspecific tags to help deliniate and reduce potential conflicts. Using cf8.1 production. Would be nice to see in cf9 Still, it would be a nice level of modularity to be able to add this feature at the application.cfc level.
Vote by External U.
24310 | November 10, 2011 07:10:24 PM GMT
I think this is a really good idea and a much-requested enhancement. It doesn't affect or interfere with the in-page <cfimport> tag, it just provides meaning for <prefix:tag> when no <cfimport> is present and could therefore be treated almost like a <cfmodule> tag invocation using /prefix as a mapping.
Vote by External U.
24311 | November 10, 2011 07:10:24 PM GMT
+1 For cfimport enhancement - I especially like the the "CSS-like" approach of it.
Vote by External U.
24312 | November 10, 2011 07:10:26 PM GMT
+1 to the import enhancement.
Vote by External U.
24313 | November 10, 2011 07:10:27 PM GMT