You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Why
xbee-java is crashing with newer java systems like JDK11. As far as I know, this only affects 64 bit versions of Java, as the rxtx library is simply too old. I know the compatibility only says Java 8, but Java 8 is no longer supported with updates. I find it an absurdity to expose software to such security risks for customers.
What
Replace the rxtx-Library with newer code libraries or write an own wrapper for it.
The text was updated successfully, but these errors were encountered:
Since there was a recent release of this library apparently development is still done on it; Please make this a priority! The only way to use the xbee-java library on recent windows version is by using an ancient JRE8 version - JRE251 from 2020 or older.
@bramvdpol i totally agree on you, but as a short fix you can replace the serial library by sacrificing the unit tests. I already did that for my master thesis, seems to work fine. Still not an elegant solution, because the tests are missing.
You could also use the 32 bit version of newer OpenJDK versions. The problem is not Java itself, only that the old serial library is only supporting 32 bit.
All right, thanks for your insight! That does provide some workarounds for the time being. I think I prefer untested code that at least runs on the latest JRE compared to the current situation. I will also look into OpenJDK, that might be the best option for now.
Thanks again!
Why
xbee-java is crashing with newer java systems like JDK11. As far as I know, this only affects 64 bit versions of Java, as the rxtx library is simply too old. I know the compatibility only says Java 8, but Java 8 is no longer supported with updates. I find it an absurdity to expose software to such security risks for customers.
What
Replace the rxtx-Library with newer code libraries or write an own wrapper for it.
The text was updated successfully, but these errors were encountered: