But did you know that this year they have added other Adobe enterprise products, including ColdFusion. There will be 16 CF sessions, all presented by members of the CF team. Some are about CF2018 but some are not.
I think most CF folks would find the low
$75 $15 price to attend (Adobe just posted this discount code: He7B52)--which includes access to the recordings of all 90 sessions--to be well worthwhile. For the sessions, speakers, and more, see below.
Wondering about CF support for Java 9, 10, or 11, here in 2018 (with respect to CF 2018, CF 2016, CF 11, or earlier)? Did you know that Java 9 and Java 10 each have only 6-month lives? Seriously. And did you know that Java 9 is already no longer updated, while Java 8 still is (into next year), and that Java 11 is due to come out in September 2018? It can be quite confusing if you've not been paying attention to Oracle's new release model.
What does all this mean for Adobe and CF, and CF users? What versions of CF do, do not, and/or may support these various recent Java versions? The good news is that CF 2018 will come out running (and the second public beta does come running) on Java 10 (no word yet on Java 11). But what about other recent CF versions?
Read on for more.
Update: CF2018 did come out as expected in July 2018, and at first it came out supporting Java 10. Then after Java 11 came out in late 2018, Adobe updated both CF2018 and CF2016 in early 2019 to support Java 11 (or you can continue to use Java 8 while it's supported by Oracle). Adobe also announced in Jan 2019 that they had reached an agreement with Oracle licensing Java for commercial use with CF. You may want to read my post on the CF portal discussing further when the April 2019 updates for Java 8 and 11 were released by Oracle.
I leave what I wrote below for posterity/historical perspective.
The first several are in fact resource lists where I pulled together resources, to help people in addressing some specific topic/challenge, which is something I enjoy doing as a contribution to the community. Sometimes the posts are related to the consulting work I do, but not always (just like some of the conference presentations I do, which are nearly always about CF, but not always about CF troubleshooting).
You'll see also a couple of posts that point to resources where I've been contributing time and content elsewhere (taking away somewhat from my posting things here). First, I've done about a dozen blog posts on the new Adobe CF Community Portal. Second, I've done about a dozen webinars for the FusionReactor folks. I've debated posting each one of those here as I did them (as blog posts here, I mean, throughout the year), but for now I had instead just opted to create a post for each of them last year listing what all I'd done.
If so, I have some very good news--and some not-so-good news. (Some may know that you can find this info also by running the CFC Explorer--more on that in a moment.) The unfortunate news is that it's not yet COMPLETELY documented, but it's still a good start.
Anyway, I have contributed several blog posts (some really article-length, and all written as standalone "articles", so I am referring to them that way here, and in my "articles" page).
I wanted to point to them out in a post here as well. I was also torn about whether to post them in their entirety here, whether before or after posting them there, but for now, I have posted the content only there.
And unlike previous Adobe cfdevweeks, which often involved non-Adobe presenters (including myself), this year's sessions were all from members of the Adobe CF team, on these topics:
We're sorry but a serious error has occurred in the system.
If this happens to you, I have a possible quick solution (if you just want to get to the page in question):
Use your browser's menu option to have it create a "new private window" (FireFox), or "new incognito Window" (Chrome), or "new session" (IE), or the like.
This will open a new window for your browser, and it will NOT send any cookies to the page in question. And you should find that suddenly the forums "work", which tells you that the problem was about the server's unhappiness with something about the cookies in your browser.
If that's enough, great. If you want to know a bit more, read on.
The first problem was introduced in the CF2016 installer released in Dec 2016, and any after that, where Adobe has literally removed the library used for the calendaring, but you can add it back, as I discuss below. (If you install or installed CF 2016 from the original installer in Feb 2016, you won't see this problem as it wasn't removed then.)
The second problem was introduced in those two named updates, and was fixed in the very next updates (CF11 update 13 or CF2016 update 5). And of course, this could also happen if you're moving to CF11 or 2016 for the first time, and someone else had "fully updated" those to that update level before you started testing against it.
If you'd like to know more, read on.