Jump to content
Excelsior Forums


Excelsior Staff
  • Content count

  • Joined

  • Last visited

Community Reputation

0 Neutral

About cypok

  • Rank

Profile Information

  • Gender
    Not Telling
  1. Error with kotlin and tornadofx

    Thank you for the sample. We have reproduced the problem and can confirm that it is a bug in our verifier. We will fix it in the next Excelsior JET release (i.e. version 14). Could you please contact us by email (java (at) excelsior-usa.com)? We can make a hotfix for the current version or suggest a workaround. P.S. gradlew.bat is useless without gradle/wrapper/gradle-wrapper.jar. It is a good idea to add the following lines to your gitignore: !gradle/wrapper/gradle-wrapper.jar
  2. org.modelmapper.PropertyMap issues

    It looks like a configuration issue if you code works fine after compilation and throws NPE while trial run in JetPackII. Maybe your application requires some configuration/property files or it depends on current directory. Does the problem reproduce after packaging ignoring results of trial run? Is it possible to add debug print in configure() method (i.e. print value of map(), map().getSomeProperty(), source)?
  3. MacOS: -Xdock:name not working

    Hello, you should use JVM options -Dapple.awt.application.icon -Dapple.awt.application.name instead of -Xdock:icon -Xdock:name for customizing your AWT application using Excelsior JET. Please note that for better user experience on OS X you may pack your application as an application bundle: https://github.com/excelsior-oss/excelsior-jet-maven-plugin#creating-os-x-application-bundles-and-installers -- Excelsior Support
  4. Usually this kind of error appears if you change some configuration files of your Tomcat application after it has been compiled using Excelsior JET. Please make sure that it is not the case. Please note that the most recent versions of Tomcat are not supported by Excelsior JET 11.0. Try to use Tomcat 7.0.59 or earlier for your application and check if error persists. Alternatively, you can try out our Excelsior JET 11.3 beta for amd64 platforms at http://www.excelsiorjet.com/beta, which has full Tomcat 7 and 8 support. Please contact us at java@excelsior-usa.com if none of these helps. -- Excelsior Support
  5. Using Excelsior JET on Linux with LDAP

    I want to add one more note about this issue: the same problems could be caused by absense of samba-winbind-modules.i686 library.
  6. Hello, Could you please contact us via email: <java@excelsior-usa.com>? Regards, Excelsior Support
  7. Hello, We need to clarify some details about your problem. It would be easier to continue our discussion if you duplicate your message to <java@excelsior-usa.com>. -- Excelsior Support
  8. JET Runtime: System Exception

    Hello!This problem needs some investigation. So please contact us at java@excelsior-usa.com. -- Excelsior support team
  9. Not able to start Excelsior-Jet

    You are welcome!
  10. Not able to start Excelsior-Jet

    Hello, We have already encountered this problem. Please try to download the latest version of Excelsior JET for OS X and install it. Please let us know if it helps. -- Excelsior Support
  11. java.lang.ClassNotFoundException

    Hello, JavaFX is not a part of Java Platform version 7 and Excelsior JET 9.0 doesn't support it. If you need more information please contact us by email: java@excelsior-usa.com -- Excelsior Support
  12. Nullpointer exceptions in 64-bit versions

    Excelsior JET 9 contains few bug fixes so I undoubtedly recommend you to recompile your application with latest JET. Also note that we cannot investigate the problem until there is a way to reproduce it. -- Excelsior Support
  13. Hello, We haven't succeeded in reproducing your issue. Could you provide us with the application bytecode on which the problem can be reproduced? Note that we do not need the full application. If the problem can be reproduced on a scaled down version of the application, that would be sufficient. You may send your application to java@excelsior-usa.com. -- Excelsior Support
  14. Can't compile Apache POI 3.9

    I've tried to compile the same application and also got this message about classes inconsistency. However you should understand that Java classes may contain links to unresolved classes and it's OK if these links are never resolved. Fortunately, the JET compiler is able to compile the application even if it comprises such classes. In your case you should treat this messages as warnings in third-party library, ignore them and continue compilation. I've successfully compiled your example and JET compiled executable runs flawlessly. For more information see JET User's Guide, Chapter "JET Control Panel", Section "Step 3: Selecting a compilation mode", Subsection "Class viewer", Paragraph "Classpath inconsistency", Subparagraph "Unresolved import". -- Excelsior Support
  15. Recompile with JDK 50

    Hello. To fix this error it should be sufficient to recompile your application (all classes & jars) with JDK 6. -- Excelsior Support