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
We sign all of our jars and all of our dependencies with our companies certificate. Running a signed JavaFX application that was packaged as a native bundle using the official FX package tools we'll get this exception:
java.lang.SecurityException: class "javafx.scene.control.Dialogs"'s signer information does not match signer information of other classes in the same package
at java.lang.ClassLoader.checkCerts(ClassLoader.java:943)
at java.lang.ClassLoader.preDefineClass(ClassLoader.java:657)
at java.lang.ClassLoader.defineClass(ClassLoader.java:785)
This is because of the same package name as the original FX source.
Do you have any plans to modify the package name to prevent this issue?
The text was updated successfully, but these errors were encountered:
In that case you could take the source and just refactor the packages. You will need to make some path adjustments in the Dialogs class.
I don't plan to put too much work in improving the dialogs, because they should be included in the JavaFX 8 release that is due this year. So I'd recommend you make a temporary solution for the next few months and then remove the library once JavaFX 8 has been released.
We sign all of our jars and all of our dependencies with our companies certificate. Running a signed JavaFX application that was packaged as a native bundle using the official FX package tools we'll get this exception:
java.lang.SecurityException: class "javafx.scene.control.Dialogs"'s signer information does not match signer information of other classes in the same package
at java.lang.ClassLoader.checkCerts(ClassLoader.java:943)
at java.lang.ClassLoader.preDefineClass(ClassLoader.java:657)
at java.lang.ClassLoader.defineClass(ClassLoader.java:785)
This is because of the same package name as the original FX source.
Do you have any plans to modify the package name to prevent this issue?
The text was updated successfully, but these errors were encountered: