Correct. Starting in 5.0 we are using a combo of jaxb + stax for XML
parsing, instead of dom4j. At the moment we have no concrete plans to do
any 4.x release with that approach, although it is one of the items we want
to discuss when we get together in a few weeks: specifically a possible
4.4/4.5 release with a *limited* subset of concepts/code ported from 5.0
back to the 4.x codebase.
On Thu, Oct 16, 2014 at 6:25 AM, Emmanuel Bernard <emmanuel(a)hibernate.org>
wrote:
Hi,
Three of these errors are related to Infinispan which you have already
contacted.
Two are related to dom4j which we use for XML parsing. While I think our
next gen version will no longer use dom4j, we don’t plan on moving away
from dom4j for the older and current releases. So I am not sure why you
guys are removing org.relaxng form the JDK but if you do then we won’t be
able to have Hibernate ORM running on JDK 9.
Emmanuel
On 10 Oct 2014, at 12:00, Rory O'Donnell Oracle, Dublin Ireland <
rory.odonnell(a)oracle.com> wrote:
> Hi Sanne,
>
> Did you have time to review the report, any feedback ?
>
> Rgds,Rory
>
> On 11/09/2014 15:14, Rory O'Donnell Oracle, Dublin Ireland wrote:
>> Hi Sanne,
>>
>> As part of the preparations for JDK 9, Oracle’s engineers have been
analyzing open source projects like yours 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. I have
prepared a report for your project release hibernate-release-4.3.6 based on
the jdeps output.
>>
>> The report is attached to this e-mail.
>>
>> For anything where your migration path is unclear, I would appreciate
comments on the JDK-internal API usage patterns in the attached jdeps
report, (if any) - in particular comments elaborating on the rationale for
them - either to me or on the adoption-discuss [1] mailing list at OpenJDK.
>>
>> 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
>> [1]
http://mail.openjdk.java.net/mailman/listinfo/adoption-discuss
>>
>
> --
> Rgds,Rory O'Donnell
> Quality Engineering Manager
> Oracle EMEA , Dublin, Ireland
>
>
>
>
_______________________________________________
hibernate-dev mailing list
hibernate-dev(a)lists.jboss.org
https://lists.jboss.org/mailman/listinfo/hibernate-dev