Jump to content
Excelsior Forums


  • Content count

  • Joined

  • Last visited


Posts posted by mavr

  1. Creating a windows is very complex task, and it is impossible to do it with xFunction. The possible (but still complex) way is to find a handle of AWT window of the Java application.  For example, ome may search for a window with a specified title (FindWindow(NULL, title)), or enumerate all windows in the system (EnumWindows). Please refer to MSDN library for details of using these functions.

  2. Then probably XAWT component is used from somewhere else.  To find the exact class that imports this DLL, you may look for its name in the body of .obj files (an easy task with FAR  ;) ). You may contact us at java@excelsior-usa.com for further help.

    The only way to manage adding of required DLLs is modification of the compilation set. In case if some small part of XAWT is really needed, while the rest is useless, it is recommended to use PERFECT compilation mode (although it is much harder and error-prone)

  3. DLLs are not resources, so they can not be jared and bound to the executable. You have 2 options how to force your executable to find these DLLs

    1) As you have done, copy the DLLs to the application directory

    2) Leave them in any directory and add that directory to %PATH% variable - either in run.bat file or globally to the system during the installation (using custom callback DLLs in case of Excelsior Installer).

  4. We had another similar report some time before, but the reason of the problem is not found yet. At this time you should use the workaround described below.

    The MP2 is already installed after the first error message (but not applied). To apply it, one should directly use jetsetup program. Due to the error, additional option -ignore-jetini should be used with jetsetup.

    1) Execute  "jetsetup -ignore-jetini -show-profiles"

    2) Choose one of displayed profiles (let it be profile 0) and run

    "jetsetup -ignore-jetini -repair-profile 0"

    3) If there is no installed profiles yet, or you wish to create a new one, use command "jetsetup -ignore-jetini -jre /usr/java/j2sdk1.5.0_03"

  5. Unfortunately, for application servers the situation differ. The server and applications still can be compiled with JET (see this Knowledge Base article, but the applications classes (.war etc.) still have to be deployed, because custom clasloaders are used. So, there is no protection of applications classes in this case.

    You may consider moving your applications to 'shared' part of the server, in this case it is safe to remove the classes from the deployment package.

  6. The total size of arguments rounded up to 4 should not be equal 12. I.e., 3 4-byte arguments (char, short, int, etc.), or 1 8-byte (e.g. double) and 1 4-byte are prohibited.

    Of course, there is no such restrictions in the commercial version.

  7. No, it is impossible.

    However, jetsetup has batch mode, so you can switch profiles from scripts. To use the batch mode, please do the following (from console):

    1) Go to jet/bin folder and execute the command "gui - jetsetup.exe"

    2) Run "jetsetup -batch -show-profiles", remember the numbers of requied profiles.

    3) Then, you may switch between the profiles by executing "jetsetup -batch -activate-profile <num>", where <num> is the number of the required profile, e.g. "jetsetup -batch -activate-profile 2"

    You need to perform steps 1 and 2 only one time. Then, you may do step 3 from the scripts of your build server as many times as required.