RE: Upgrade path to ColdFusion (2018 release)

This post is regarding the "Upgrade path to ColdFusion (2018 release)" post at the ColdFusion Community Portal. It looks like Adobe's website only offers the ColdFusion (2016 release) full license and not the upgrade license?

Steps to Reproduce: 1) Visit www.coldfusion.com
2) See this:

3) Click any of the "Buy Now" buttons
4) See this:

5) Go back www.coldfusion.com and scroll to the bottom
6) See this:

7) Click the Standard Edition's "Buy Now" button
8) See this:

Question: How does one choose the upgrade license?

CF-4202597 - per-app mappings don't exist in REST CFCs

Issue: per-app mappings don't exist in REST CFCs

Steps to Reproduce:
1) unzip CF-4202597.zip (attached to ticket)
2) run index.cfm to register REST app
3) run mypage.cfm

Actual Result: coldfusion.xml.rpc.CFCInvocationException - Could not find the ColdFusion component or interface mymapping.myOtherCFC

Expected Result: "c"

4) In CF Admin, create "mymapping" mapping to unzipped app's directory
5) run mypage.cfm

Actual and Expected Result: "c"

Verified in build 2018.0.01.308605 (PreRelease).
Filed as CF-4202597.

CF-4202547 - CF2016 vs Aether wrt custom REST response via cfthrow

Issue: CF2016 vs Aether wrt custom REST response via cfthrow

History: Pre-Aether, cfthrow could be used to send a custom REST response as JSON. In Aether, this fails (returns HTML of error handler page).

Steps to Reproduce:
1) Unzip CF-4202547.zip (attached to ticket)
2) Run index.cfm to register the REST application
3) Run mypage.cfm and compare the output w/ the code comments in mypage.cfm

Actual Result: CF sends cfthrow's custom message as HTML of error handler page

Expected Result: CF sends cfthrow's custom message as JSON

Related URL: Getting Started with RESTful Web Services in ColdFusion

Verified in build 2018.0.01.308605 (PreRelease).
Filed as CF-4202547.

Summary:

Initially:
1) In non-void UDF, restSetResponse() was ignored
2) In void UDF, cfthrow returned custom REST response as HTML of error handler page (instead of JSON)

Both were filed as CF-3546046, but only #2 was fixed (which I've verified in CF2016 Update 1).

#1 was re-filed as CF-4198298.

In Aether Public Beta Update 1, #1 is fixed but #2's fix was reverted/undone/unfixed.

Filed CF-4202547 to re-fix #2.

CF-4202540 - standard attribute notation doesn't override JavaDoc notation

Issue: standard attribute notation doesn't override JavaDoc notation

Note: The "Defining components and functions in CFScript" doc says "Attribute values set in the element declaration take precedence over the values set in the comment section. Therefore, if you set an attribute, such as a hint in both locations, ColdFusion ignores the value in the comment section and uses only the one in the element declaration.".

Note: Lucee correctly behaves as per that doc.

Repro:

<cfscript>
  /**
  *@description original description
  *@displayname original displayname
  *@hint original hint
  *@output false
  *@roles original,roles
  */
  public function foo() description="overridden description" displayname="overridden displayname" hint="overridden hint" output=false roles="overridden,roles" {}
  writeDump(foo)
</cfscript>

Actual Result: coldfusion.compiler.DuplicateAttributeException

Expected Result (and actual behavior w/ Lucee):

function foo
Arguments: none ReturnType: Any Roles: overridden,roles Access: public Output: false DisplayName: overridden displayname Hint: overridden hint Description: overridden description

Related URL: Defining components and functions in CFScript

Verified in build 2018.0.01.308605 (PreRelease).
Filed as CF-4202540.