Jump to content
Excelsior Forums


Excelsior Staff
  • Content count

  • Joined

  • Last visited


Posts posted by Nastia

  1. Hi,

    JetPackII projects should not be modified manually. JetPackII uses relative paths if possible (relative to the project root directory within one disk). The solution may be to create a script that copies the jpn project files to the root project directory, build the package and then delete the project file. Is it suitable for you?

    We plan to solve this limitation (relocation of jpn projects) in the next version of Excelsior JET.

  2. Hi,

    JetPackII automatically recognizes multi-app executables and prompts you to make the necessary installation settings. You don't need to create any additional projects.

    I tried to follow the directions from the on how to do this but when I went to Jet Pack I could not see that it detected the the mult-app capability of my executable.

    Could you please explain the problem in more details? Why do you suppose that JetPackII didn't detect that your application was compiled in multi-app mode?

  3. Yes, Excelsior JET can help improve the startup time.

    Please create a JET project for your application (use the JET launcher). In the JET Control Panel test the application thoughtfully on the Testrun page (step 2). Then compile the project and proceed to create a deployment package with JetPackII.

    Select "self-contained directory" as a back-end in JetPackII. The directory named  ?<project name>-native? will be created. You may copy this directory anywhere (for example to the CD) and then run the compiled application which is inside this directory, no JRE is required. You may create a script to invoke this executable and call this script from Autorun.inf file.

  4. The problem appears because java.util.logging requires the stack trace information.

    Please open your project with the JET Control Panel, go the Target page and set the stack trace support to "minimal". Then recompile the project (F9).

  5. Hi,

    Could you perform two experiments on your Linux system where the problem occured (under the root account)?

    Please look at this Linux issues:



    In these issues you can find the simple test which demonstrates the bug.

    Do the tests crash on your machine?

    These bugs are known to be able to affect execution of jet-compiled executables in the way they can crash with "Runtime error #3 (trap)".

  6. Hi John,

    I have tried to reproduce on Linux the problem you reported, but I have not managed to do that. (I was using the same scenario as for Windows.) Could you please describe it in more details? I need to know: what is the old JET version (4.5 ?),  new version (6.4 or 6.4 MP1, Java 6 update 7 or update 10?).

  7. Hi, thank you for your inquiry.

    >>1) in .prj files, is it possible to define classpathentries for all jar files in a given dir?

    At present It is not possible to do with the JET Control Panel. There is a non-documented option that can be used for this goal. However if you use it, you won't be able to open a project with GUI interface and you will need to modify it manually. So I would recommend you to create a project with the JET Control Panel first and then add the following lines


    !batch *jar <Directory Name>

    where <Directory name> contains the jars to be compiled.

    May I ask you, do you plan to change the content of this directory or do you need to create it once?

    2) You are right, JetPackII projects should not be modified manually.

    >>Therefore, is it possible to *generate* the jpn file from the .exe on the commandline?

    No. The compiled application doesn't  contain the full information for deployment.

    >>This would let me fully automate the process and be able to run it on a different machine without modifications.

    If you create a JetPackII project with all the paths relative to the root directory, then you will be able to build this project on any machine with the same folder structure. What modifications do you mean?

  8. Hi,

    No, Excelsior Installer cannot do it automatically. But you can implement this functionality by writing your code (e.g. in C), compiling it to a callback DLL and then using it in the Excelsior Installer. 

    For the detailed information please refer to the JET User's Guide, Chapter "Deployment Automation", Section "Excelsior Installer", subsection " Callback DLLs" and Section "Specifying Installation Setings", subsection "Extra-facilities".

  9. Hello Bryan,

    Could you please run your application under the Sun JRE on the same system where the compiled application fails. It might help to understand if the problem is related to Excelsior JET or not. If your application runs properly under the Sun JRE, please perform the Test Run of your application on the same system using JET Control Panel. (You should install Excelsior JET on that system for this testing) Open the project you used to compile your application with JET Control Panel, go to the step 2 and perform the Test Run. Does the application work properly?

  10. Hello Bryan,

    There are no any known problems related to?using SWT with Excelsior JET.

    Excelsior JET has passed the Sun's Java Compatibility Kit test suite

    and moreover we have thoroughly tested JET to run the applications that use SWT.

    I cannot give you an advice that might help without knowing the problem details.

    Could you please answer the following questions:

    -- Does the application work properly under Sun JRE? (on the same systems where the compiled application fails)

    -- How the compiled application fails? What are the exceptions thrown, what is printed to the console?

    -- On which system the compiled application fails to run? (the same system where you compile the application or another system to which you deploy the compiled application, hardware & OS).

    -- Did you use JETPackII to deploy the application to the other systems?

    -- What is the JET version you use?

  11. Hello,

    You can use the following script to launch NetBeans5.0 from the command line

    SET JDK_DIR=C:\jdk1.5.0_06

    SET NETBEANS_HOME=C:\netbeans-5.0

    %JDK_DIR%\jre\bin\java.exe "-Dnetbeans.importclass=org.netbeans.upgrade.AutoUpgrade" "-Dnetbeans.accept_license_class=org.netbeans.license.AcceptLicense" "-Xms32m" "-Xmx128m" "-Dapple.laf.useScreenMenuBar=true" "-Dnetbeans.osenv=%TMP%\nbenv2" "-Dnetbeans.osenv.nullsep=true" "-Djdk.home=%JDK_DIR%" "-Dnetbeans.home=%NETBEANS_HOME%\PLATFORM6" "-Dnetbeans.dirs=%NETBEANS_HOME%\nb5.0;%NETBEANS_HOME%\ide6;%NETBEANS_HOME%\enterprise2;%NETBEANS_HOME%\harness" "-Dnetbeans.user=%USERPROFILE%\.netbeans\5.0" "-Dnetbeans.system_http_proxy=DIRECT" "-Dsun.awt.keepWorkingSetOnMinimize=true" -cp "%NETBEANS_HOME%\PLATFORM6\lib\boot.jar;%NETBEANS_HOME%\PLATFORM6\lib\org-openide-modules.jar;%NETBEANS_HOME%\PLATFORM6\lib\org-openide-util.jar;%JDK_DIR%\lib\dt.jar;%JDK_DIR%\lib\tools.jar" org.netbeans.Main

    Note that NetBeans is a Java application that extensively loads classes dynamically using custom classloaders. To compile and optimize all classes including those loaded dynamically one should first collect the JITCache and compile it. For more information on this task please refer to the article?


  12. Hello,

    Unresolved import dependencies may result in throwing "NoClassDefFoundError"

    at run time if your application tries to access one of the absent classes listed

    in the warning message.

    The dynamic nature of Java permits using inconsistent jars and classes.

    Please note that absent classes may be generated during run time or

    "NoClassDefFoundError" may be successfully caught by the Java code.

    So unresolved import dependencies don't necessarily mean an error.

    The JET Control Panel shows this warning message for you to be sure that

    none of the listed classes should be included to your application.?

    As for third-party libraries the only option is to ignore the inconsistencies.

    You may also file a complaint to vendors of such jars.

  13. Hello Rob,

    Some our customers reported the similar problem.

    It was caused by conflicts between the JET-compiled executable and

    HP Share-to-Web application. The problem went away after uninstalling the latter.

    We plan to start investigating this problem in the near future.

    Do you have this program installed on your computer?

  14. Hi!

    Most probably the problem is in your application, not in the JVM.

    If you need help to debug your application you can benefit from Excelsior professional services.

    Excelsior provides custom services: developing various applications, improving performance and stability of existing Java applications, porting legacy applications to modern languages, etc.

    For more details see http://www.excelsior-usa.com/services.html .

    BTW, did you try Excelsior JET to run your application? Does it fail too?

    I recommend you to try the latest JET version (4.1) with all available updates

    http://www.excelsior-usa.com/jetdleval.html .