IMPORTANT DEPRECATION ANNOUNCEMENT: Updates to COM/DCOM, Axis1, SharePoint

[Saurav_Ghosh]

We would like to inform users that certain previously deprecated features and associated dependencies will be removed in the next bug fix update. This is part of our efforts to enhance security, performance, and modernization.  

History 

We previously announced the removal of deprecated features before ColdFusion 2025's release. See the following for more information: 

• Community forum blog 

• Deprecated features in ColdFusion 

What will be removed in the next bug fix update* 

Feature	ColdFusion 2025	ColdFusion 2023	ColdFusion 2021
COM/DCOM	Removed	Will be removed in the next bug fix update.	Will be removed in the next bug fix update.
Axis1	Removed	Will be removed in the next bug fix update.	Will be removed in the next bug fix update.

* Tentatively planned for Q1, 2026 

 Axis1 

The web service versioning when set to WSVersion = 1 will no longer be supported in future releases. This change is aligned with the removal of support for Apache Axis 1.x, which has limited usage now. 

See CreateObject webservice documentation for more information on creating a web service object in ColdFusion. 

Rich text editor support 

We are currently assessing phasing out rich text editor feature, through the cftextarea tag, provided by CKEditor. This evaluation aligns with our broader efforts to modernize the ColdFusion platform and further improve security and performance. 

If your applications use a rich text editor through the cftextarea tag (see code below), either directly or through embedded functionality, we welcome your feedback to help us assess the potential impact.  

Share your inputs with us at cf-deprecation@adobe.com

<cfform name="myForm"> 
  <cftextarea name="x" richtext="yes">  
     some content  
  </cftextarea> 
</cfform>

SharePoint integration 

The removal of support for Axis1.x and the associated security concerns also impacts the ColdFusion SharePoint integration. This integration has supported on-premises services provided by SharePoint. 

The future development of SharePoint will primarily focus on online services. As a result, we are considering deprecating the SharePoint On-Premises Services integration. If this impacts your applications, please share your inputs with us at cf-deprecation@adobe.com. 

For more information on the ColdFusion SharePoint integration feature, refer to the documentation on SharePoint with ColdFusion. 

Reason for deprecation 

The main reasons for deprecating these features are as follows:  

• Security vulnerabilities associated with these features.

• Some features are no longer supported. 

• Limited usage of these features. 

• The need to update and streamline our framework to ensure better performance and scalability. 

Next steps 

We encourage all users to review their applications and plan for these upcoming changes. Should you have any questions, concerns, or require assistance during this transition, please do not hesitate to contact us at cf-deprecation@adobe.com. 

We appreciate your continued support as we evolve ColdFusion to meet modern development needs. 

[Tim2842955474bi]

Can we get an update on the ETA for this change? Also no one ever replied when I emailed cf-deprecation@adobe.com a few months ago 🙂 . We are trying to work on moving our customers off of Axis1 on CF2023. Better communication would be great. 

[Charlie Arehart]

It's not clear if you saw the indication about halfway down the page that the axis1 removal from 2023 is "* Tentatively planned for Q1, 2026". (As for cf2021, it's hard to imagine Adobe updating it in 2026, with its EOL having been earlier this week) 

Perhaps you mean you want a more specific date than that. Adobe never has announced update dates in advance, that I've seen. Indeed, this q1-26 announcement is itself unusual.

If you're main goal is looking for motivation to get your clients to fund changing your cf2023 app to stop relying on axis1, that indication would surely seem strong enough, as-is. 🙂

But I know you'll want to hear from Adobe instead. I'd recommend you email that address again, simply asking if anyone is seeing it (keep it simple to reply to).