portal entry

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

Oracle Java support for Adobe ColdFusion

| View in Portal
January 24, 2019 04:20:05 AM GMT
29 Comments
<p>We have some positive news to share with you! Support and distribution of Oracle Java SE, including all maintenance updates of Long-Term Support (LTS) releases (Oracle Java SE 8 and Oracle Java SE 11), will be supported by Adobe directly for all ColdFusion customers making use of the Oracle Java technology. All customers will need to abide by Oracle’s terms of use as they have previously. The support covers the use of all Oracle Java SE releases, current and future, for ColdFusion […]</p>
<p>The post <a rel="nofollow" href="https://coldfusion.adobe.com/2019/01/oracle-java-support-adobe-coldfusion/">Oracle Java support for Adobe ColdFusion</a> appeared first on <a rel="nofollow" href="https://coldfusion.adobe.com">ColdFusion</a>.</p>
Labels: Adobe ColdFusion, Blog, Uncategorized

Comments:

Thank you for the update!
Comment by WilzDezign
1573 | January 24, 2019 05:52:07 AM GMT
Great news!
Comment by Michael Thomas
1576 | January 24, 2019 11:35:41 AM GMT
Thank you Rakshith and the Adobe CF team, this is the best possible outcome.  It's also good news that you'll be making CF 2016 compatible with Java 11 too. Do you recommend customers to upgrade to Java 11 and what are the key benefits please? (Presumably an upgrade guide will be provided with the next CF update?) Thanks again.
Comment by Gary Fenton
1577 | January 24, 2019 12:36:10 PM GMT
Rakshith: Thanks for the update on this. To be completely clear, does this also mean that use of Oracle's Java SE 8 and 11 in production environments, when used with Adobe ColdFusion, is allowed without the Adobe customer purchasing a separate license from Oracle for that Java use?
Comment by Ron.Stewart
1585 | January 24, 2019 12:40:07 PM GMT
This is good news.  Thank you Adobe.
Comment by Miguel Fernandez
1584 | January 24, 2019 01:00:26 PM GMT
Great news Rakshith and Team! I do have one question, once the Java 8 release ends public updates (after January 2019), how does a ColdFusion customer download them? For Java 7 and below the <em>non-public</em> updates are only avaliable if you login to Oracle to download them.
Comment by Peter Freitag
1579 | January 24, 2019 02:50:47 PM GMT
Great news Rakshith! Will there be a ColdFusion portal for getting the latest Java SE / JDK LTS versions from Adobe?
Comment by jbrock777
1582 | January 24, 2019 03:00:43 PM GMT
This is good to hear, I am sure many people were worried in limbo and were awaiting this announcement before making decisions.
Comment by Tyler Clendenin
1580 | January 24, 2019 03:10:39 PM GMT
Yes, we will soon announce the portal details where you can download Java SE versions that can be used with ColdFusion.
Comment by Rakshith Naresh
1587 | January 24, 2019 05:07:52 PM GMT
Pete, we will make available all the subsequent updates ,post the end of public updates, to ColdFusion customers.
Comment by Rakshith Naresh
1590 | January 24, 2019 05:11:24 PM GMT
Absolutely, Ron!
Comment by Rakshith Naresh
1589 | January 24, 2019 05:12:15 PM GMT
Gary, I recommend moving to Java 11 as it is the latest LTS release from Oracle. We will communicate the benefits in our tech note associated with the Java 11 support update.
Comment by Rakshith Naresh
1588 | January 24, 2019 05:15:26 PM GMT
Yep, really wonderful news to hear--and folks should read the comments here, which make some things more clear: that we will not need to purchase from Oracle either support for updates to Oracle Java 8 (which will no longer be free publicly after this month), nor to license Oracle Java 11 in production (also not free otherwise). Some may not quite see this as what Rakshith's is saying, as he says that we who are using CF would be  "supported by Adobe directly" to get Java 8 updates and use Java 11 . That phrasing left questions, and Rakshith clarified them in answers/comments here. I have also updated <a href="https://www.carehart.org/blog/client/index.cfm/2018/11/15/on_production_use_of_java_going_forward" rel="nofollow">my blog post talking about the issue</a> (for those to whom this whole java 8/11 licensing question may be news). Thanks very much, Rakshith and to the CF team and management for solving this for us.
Comment by Charlie Arehart
1591 | January 25, 2019 01:27:34 AM GMT
Great news Rakshith and CF Team.
Comment by Benjamin Reid
1592 | January 25, 2019 02:14:33 AM GMT
Great news - thanks so much!
Comment by Phillip Chrisman
1596 | January 25, 2019 03:20:55 AM GMT
It would be nice to (eventually) get a clear definition of what "for ColdFusion customers to run their ColdFusion applications" means. For example, we have developed substantial amount of custom Java code for use as part of our CF apps. We access the code from CF via CreateObject("java"...) and other mechanisms that allow bridging CF and Java. I would think that this clearly counts as part of "running a CF application", but there can be less clear situations. I would also like to know if the ability to download Java updates will be restricted to purchasers of currently supported CF versionsonly (11, 2016, 2018). We have some unsupported versions in production (10, 11) running on Java 8. While I don't expect CF to support these versions of CF as such, would we be at least entitled to download the updates for Java 8 (and use at our own risk)?
Comment by Legorol San
1598 | January 26, 2019 02:58:28 AM GMT
Minor correction: I meant to write supported CF versions (2016, 2018), unsupported version (10) and very soon unsupported (11). In other words this is a pertinent question for CF 11 users as well, will we still be able to download Java 8 updates after CF 11 support ends?
Comment by Legorol San
1599 | January 26, 2019 03:01:04 AM GMT
Hi Rakshith, I couldn't succeed settling up data source,  any help?
Comment by yogeshsurati
1607 | January 29, 2019 04:21:48 PM GMT
Yogesh, what has that question to do with this blog post? You should create a "question" (instead of a comment on a blog post). And beyond that  please add there more detail on what you are seeing, the version of cf, and so on.
Comment by Charlie Arehart
1608 | January 29, 2019 08:01:27 PM GMT
Many thanks for this information, Rakshith. I'd be very grateful if you could clarify just one more thing. For those of us who have manually updated Java for CF, where the update is installed outside the ColdFusion root, e.g. C:\Java\jdk1.8.0_191\jre is this covered under Adobe's agreement with Oracle,  or do updates need to be installed within the ColdFusion installation root (C:\ColdFusion2016\jre)? (I should add that the updated version installed outside the CF root is used exclusively on the server for CF and the CF-packaged version of Jetty).
Comment by Michael Clark
1609 | January 30, 2019 06:19:09 PM GMT
Good, so this means we can stick with Java 8? We have some compiled third-party code, which would break if there was a new Java version required in a future update. So I am glad to here we can stick with Java 8 (unless I misunderstood).
Comment by kevinbenore
1611 | January 31, 2019 04:34:18 PM GMT
Michael, I realize you will want to hear from Adobe, or better to see the legal terms. But as this is about covering use of Java by CF, I can't imagine it would somehow be tied to the directory where Java is installed, but instead only to its use by CF (and that bundled jetty server for the Add-on service, only). To give still more credence to this, note that Adobe DOES recommend we keep the JVM updated (to the latest minor release of the major release supported by a given CF version and update), and when they tell us to update Java, they DO tell us to install it where it normally goes--outside of the CF folder. (FWIW, some folks have mistakenly told their Java installer to implement itself within CF, leading often to trouble. If nothing else, it's also then impossible to easily revert back to the previous Java version.) So again, bottom line, I realize you need to hear it from Adobe, but it would be shocking if somehow the license was tied to "where" Java was installed. But your covering bases, so I understand the question. :-)
Comment by Charlie Arehart
1612 | January 31, 2019 06:48:06 PM GMT
Kevin, I realize you are asking Adobe, but since it's in reply to my comment I'll just add that the answer would seemingly be yes, unless you mean that "compiled third-party code" was being used OUTSIDE of CF. If you mean only that you'd call those Java objects from within CFML, then yep this license covers the use of Java by CF. Still, I suppose (like Michael Clark's question above about whether it matters "where" Java is installed), you are just covering your bases. Let's see what else Adobe may say.
Comment by Charlie Arehart
1613 | January 31, 2019 06:52:03 PM GMT
Thanks for commenting, Charlie. I'm aware of all the points you make, and as you mentioned, all I'm looking for is the legalese to just confirm what we pretty much know.
Comment by Michael Clark
1619 | February 05, 2019 07:51:11 AM GMT
Thank you for clarifying that Rakshith!
Comment by Peter Freitag
1621 | February 05, 2019 03:42:13 PM GMT
Thank you, Rakshith!
Comment by Lance Smith
1625 | February 05, 2019 08:00:15 PM GMT
Michael, so long as Java is solely used within the ColdFusion context, you should be fine. The directory where you install should not be a problem.
Comment by Rakshith Naresh
1632 | February 06, 2019 07:43:49 AM GMT
Legoral San, as long as every Java access is from within a CF application, you are fine. You can use Java on unsupported ColdFusion versions too at your own risk. I will recommend that you move them to supported versions as soon as possible.
Comment by Rakshith Naresh
1631 | February 06, 2019 07:47:10 AM GMT
Great to hear that, Rakshith. Many thanks for responding.
Comment by Michael Clark
1637 | February 06, 2019 04:34:52 PM GMT