Please check the latest EPICS Java announcement mail [1] for download instructions and places.
We will try to make the Java distribution more visible on the EPICS web site [2] - remember the web site is mostly voluntary work with not too much help from the community (yet).
Cheers,
~Ralph
On 08/19, Gofron, Kazimierz via Tech-talk wrote:
> The problem is in the epics-pvaccess-5.1.1.jar. Were these jar files created with Java 8?
>
> kaz@kaz-desktop:/epics/utils/ADViewers/ImageJ/EPICS_areaDetector$ strings epics-pvaccess-5.1.1.jar | grep BlockingTCPConnector
> org/epics/pvaccess/client/impl/remote/tcp/BlockingTCPConnector$TransportFactory.class
> org/epics/pvaccess/client/impl/remote/tcp/BlockingTCPConnector.class
> org/epics/pvaccess/client/impl/remote/tcp/BlockingTCPConnector$TransportFactory.classPK
> org/epics/pvaccess/client/impl/remote/tcp/BlockingTCPConnector.classPK
Where's the source code for the epics-pvaccess-5.1.1.jar? Is it the
following?
https://github.com/epics-rip/pvAccessJava/tree/5.1.1
If so, that code contains three classes that reference classes in the
org.omg.CORBA package that have been removed in Java 11:
src/org/epics/pvaccess/impl/remote/IntrospectionRegistry.java
src/org/epics/pvaccess/util/IntHashMap.java
src/org/epics/pvaccess/util/ShortHashMap.java
I don't know anything about pvAccessJava, but if the latest version is
at
https://github.com/epics-base/epicsCoreJava
then a search for "corba" there shows that it does not contain
references to classes in the org.omg.CORBA package, so if you can
upgrade to a newer version of pvAccessJava that does not reference CORBA
classes, then I think the problem would go away.
Another solution would be to add JARs to the Java classpath providing
the CORBA classes such as from JacORB:
https://github.com/JacORB/JacORB
Yet another solution would of course be to use a Java 8 VM instead of a
Java 11 VM.
Lewis