tracker issue : CF-3037535

Problem:

Instead of building new implementations of tags as functions, give us an import ability so we can import our custom tags using a prefix and closure-like syntax. ColdFusion could then automatically import all tags under the cf: prefix. All other custom tags would then be available as well as CF's tags.

This is really super-critical because without it we lose the ability to use custom tags without building a tag-based cffunction wrapper to access them. Without this, a critical portion of ColdFusion's code reuse and high-level funcitonality is gone for those using script-based syntax.

Case in point: Model-Glue uses a custom tag to render views. Were MG build in script, either one CFC would have to be different than the rest and use tags, or the custom tag idea would have to go right out the window.

Sample syntax:

//import my custom form-building custom tag widgets
import path="/custom_tags/myBiz/formWidgets" prefix="frm";

frm:form(action="/myProcessor.cfm",method="post") {
   frm:input(type="text",name="email",validateAs="emailAddress");
   frm:select(name="sel",query="qry") {
      frm:option(displaycolumn="name",valuecolumn="id");
   }
}

// use a built-in CF tag that's automatically imported to cf:
cf:query(datasource="myDsn",name="variables.user") {
   select * from user where userid =
   cf:queryparam(value="#user.getId()#",cfsqltype="cf_sql_integer");
}
Method:


Result:

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

Watson Bug ID:	3037535

External Customer Info:
External Company:  
External Customer Name: Jared C Rypka-Hauer
External Customer Email: 08C411A143BC38A7992016B6
External Test Config: 02/11/2009

Attachments:

Comments: