JDK6 vs JDK 7 and higher and certs -- JAVA400-L

× The internal search function is temporarily non-functional. The current search engine is no longer viable and we are researching alternatives.
As a stop gap measure, we are using Google's custom search engine service.
If you know of an easy to use, open source, search engine ... please contact support@midrange.com.

Subject: JDK6 vs JDK 7 and higher and certs
From: Rob Berendt <rob@xxxxxxxxx>
Date: Fri, 25 Mar 2016 09:27:25 -0400
List-archive: <http://archive.midrange.com/java400-l/>
List-help: <mailto:java400-l-request@midrange.com?subject=help>
List-id: Java Programming on and around the IBM i <java400-l.midrange.com>
List-post: <mailto:java400-l@midrange.com>
List-subscribe: <http://lists.midrange.com/mailman/listinfo/java400-l>, <mailto:java400-l-request@midrange.com?subject=subscribe>
List-unsubscribe: <http://lists.midrange.com/mailman/options/java400-l>, <mailto:java400-l-request@midrange.com?subject=unsubscribe>

We're undergoing an audit and we've discovered some expired
certifications. I'm working on that.
However, while doing a search for "path does not chain with any of the
trust anchors" on Google I got a bunch of hits on how people changed from
JDK6 to JDK7 and had to reimport certificates.
Was that something unique to just these other platforms?
I do recall hearing that JDK was full of holes and archaic to develop to
and that's why the big push to higher levels (and why IBM i 7.2 will be
the last release to support JDK 6).

Rob Berendt

As an Amazon Associate we earn from qualifying purchases.

This mailing list archive is Copyright 1997-2024 by midrange.com and David Gibbs as a compilation work. Use of the archive is restricted to research of a business or technical nature. Any other uses are prohibited. Full details are available on our policy page. If you have questions about this, please contact [javascript protected email address].

Operating expenses for this site are earned using the Amazon Associate program and Google Adsense.