Registered User
Nbr post: 8
Register: 7/30/05
|
|
Posted: 4/4/18, 8:37 AM
|
|
|
Not really a bug as such, but rather a heads up..
I updated to version 9 of the java development kit a few days ago (which also includes the runtime environment) and found this morning that the I couldnt bring up magelo to sync. I ended up reinstalling magelo and when that didnt work, I reverted back to version 8 and it now works fine again.
I'm certainly not an expert in this but when I googled the error message in the log file :
Caused by: java.lang.ClassNotFoundException: sun.misc.BASE64Decoder
it led me to a thread that pointed me to this article:
http://www.oracle.com/technetwork/java/faq-sun-packages-142232.html
So you might want to amend your Technical requirements on https://eq.magelo.com/magelo_sync.jspa
|
|
|
|
Admin
Nbr post: 11467
Register: 5/4/01
|
|
Posted: 4/14/18, 9:25 PM
|
|
|
|
Let me fix that issue shortly, I guess they have removed the base64decoder package from sun which makes sense. Should be an easy fix.
|
|
|
|
Admin
Nbr post: 11467
Register: 5/4/01
|
|
Posted: 4/16/18, 4:13 AM
|
|
|
I speak a little bit too soon, this is a more complicated than I anticipated. it turns out that Java9 will never be mainstream however and only when Java 10 will be GA (Sept 2018) will we really have an issue.
I will start working on removing those sun dependencies soon. Thanks for the reminder in any case !
For reference:
> https://blog.codefx.org/java/java-9-migration-guide/
|
|
|
|
Admin
Nbr post: 11467
Register: 5/4/01
|
|
Posted: 4/16/18, 4:35 AM
|
|
|
|
The core issue btw is with the new module system which now protect private packages such as sun.* from being accessible from the outside world.
|
|
|
|
