[
https://issues.apache.org/jira/browse/CXF-6008?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Daniel Kulp resolved CXF-6008.
------------------------------
Resolution: Not A Problem
Assignee: Daniel Kulp
Fix Version/s: Invalid
Not an issue for CXF
> Analysis of CXF dependency on JDK-Internal APIs
> -----------------------------------------------
>
> Key: CXF-6008
> URL: https://issues.apache.org/jira/browse/CXF-6008
> Project: CXF
> Issue Type: Improvement
> Components: Core
> Reporter: Rebecca Searls
> Assignee: Daniel Kulp
> Fix For: Invalid
>
>
> >>>> As part of the preparations for JDK 9, Oracle’s engineers have been
> >>>> analyzing open source projects to understand usage.
> >>>> One area of concern involves identifying compatibility problems, such as
> >>>> reliance on JDK-internal APIs.
> >>>>
> >>>> Our engineers have already prepared guidance on migrating some of the
> >>>> more common usage patterns of JDK-internal APIs to supported public
> >>>> interfaces. The list is on the OpenJDK wiki [0], along with instructions
> >>>> on how to run the jdeps analysis tool yourself .
> >>>>
> >>>> As part of the ongoing development of JDK 9, I would like to encourage
> >>>> migration from JDK-internal APIs towards the supported Java APIs.
> >>>>
> >>>> For anything where your migration path is unclear, (the JDK-9 team would
> >>>> like)
> >>>> comments on the JDK-internal API usage patterns - in particular
> >>>> comments elaborating on the rationale
> >>>> for them - either to me, "Rory O'Donnell Oracle, Dublin Ireland"
> >>>> <[email protected]>, or on this list, "Dalibor Topic"
> >>>> <[email protected]>.
> >>>>
> >>>> Finding suitable replacements for unsupported interfaces is not always
> >>>> straightforward, which is why I am reaching out to you early in the JDK
> >>>> 9 development cycle so you can give feedback about new APIs that may be
> >>>> needed to facilitate this exercise.
> >>>>
> >>>> Thank you in advance for any efforts and feedback helping us make JDK 9
> >>>> better.
> >>>>
> >>>> Rgds,Rory
> >>>>
> >>>> [0]
> >>>> https://wiki.openjdk.java.net/display/JDK8/Java+Dependency+Analysis+Tool
> >>>>
> >>>> --
> >>>> Rgds,Rory O'Donnell
> >>>> Quality Engineering Manager
> >>>> Oracle EMEA , Dublin, Ireland
> On 16/09/2014 18:59, Rebecca Searls wrote:
> > I ran jdeps on apache CXF ( http://git-wip-us.apache.org/repos/asf/cxf.git,
> > branch 3.0.x-fixes)
> > and got the following results.
> >
> > ---
> > digraph "ehcache-2.8.1.jar" {
> > // Path:
> > ./services/sts/sts-war/target/SecurityTokenService/WEB-INF/lib/ehcache-2.8.1.jar
> > "net.sf.ehcache.pool.sizeof.UnsafeSizeOf" -> "sun.misc.Unsafe
> > (JDK internal API (rt.jar))";
> > }
> >
> > ---
> > digraph "woodstox-core-asl-4.3.0.jar" {
> > // Path:
> > ./services/sts/sts-war/target/SecurityTokenService/WEB-INF/lib/woodstox-core-asl-4.3.0.jar
> > "com.ctc.wstx.msv.GenericMsvValidator" ->
> > "org.relaxng.datatype.Datatype (JDK internal API (tools
> > .jar))";
> > }
> >
> "Balchandra Vaidya" <[email protected]> wrote ..
> >
> > Thank you for the report. Both sun.misc.Unsafe and
> > org.relaxng.datatype.Datatype
> > are JDK-internal APIs that have no supported replacements. If you are
> > unable to
> > migrate away, please provide us with an explanation.
> Would the CXF team respond to the JDK-9 team about their use of these 2 APIs?
--
This message was sent by Atlassian JIRA
(v6.3.15#6346)
