[infinispan-dev] All jars must go?

[Dan Berindei]

On Thu, May 4, 2017 at 7:22 PM, Sanne Grinovero <sanne at infinispan.org> wrote:
> On 4 May 2017 at 12:03, Dan Berindei <dan.berindei at gmail.com> wrote:
>>
>> Personally I'm more worried about how our externalizers for JDK
>> classes are going to work: it's going to be hard to say we support
>> Java 9 and at the same time ask users to add a bunch of --add-opens
>> [1] to their JVM arguments. I stopped updating the POM comment at some
>> point, but most other requirements for access to private JDK fields
>> seem to come from WildFly/Pax Exam.
>
> Using "add-opens" is not the only option, and I agree it's not
> desirable - especially for embedded users.
>
> Read the Hibernate blog for some alternatives, but hey yes the APIs
> will have to change ;)
>  - http://in.relation.to/2017/04/11/accessing-private-state-of-java-9-modules/
>

Both methods seem to require the cooperation of the module containing
the POJOs. In our case those modules are in the JDK, and I doubt
Oracle will be so kind as to open everything to org.infinispan.core ;)

Dan