Jump to content
Excelsior Forums


Excelsior Staff
  • Content count

  • Joined

  • Last visited

Posts posted by snowman

  1. The just released Excelsior JET 7.0 beta 3 adds Tomcat support to the JET Control Panel and introduces the capabilities to hide the Tomcat server's [tt]conf/[/tt] directory and its contents, extend its boot classpath, change the main class and the Windows service main class, and specify additional VM options. You still have to resort to the command-line [tt]xpack[/tt] tool for packaging your Tomcat Web applications.

    Beta 3 also supports more recent Java versions: Java SE 6.0 Update 16 (1.6.0_16) and J2SE 5.0 Update 21 (1.5.0_21).

    Download Excelsior JET 7.0 beta 3 for Windows

    Download Excelsior JET 7.0 beta 3 for Linux

  2. Disclaimer: I am not a lawyer.

    To the best of my knowledge, the Apache License and EPL are both compatible with Excelsior JET license, because, unlike GPL, they do not force you to use them for your product.

    For the avoidance of doubt, your binary will include the Excelsior JET Runtime, so you may not release it as a whole under any open-source license.  Even if your source code is available under Apache or EPL, you have to use a separate binary license that does not permit reverse engineering and otherwise complies with the Excelsior JET license.

    Again, if in doubt, talk to a lawyer.

  3. You need to rename [tt]bin/xm.*[/tt] as well.

    Have no idea why unpacking the TSCP did not work. Unpack it into an empty directory and verify if [tt]bin/xm[/tt] files are identical.

    IIRC [tt]EXPORT QUALIFIED[/tt] is not part of ISO Modula-2. I'd say it is superfluous - just use qualified import.

  4. Excelsior JET is just another compatible Java SE implementation, not a silver bullet. If something is broken in HotSpot VM, chances are good that it is not broken in Excelsior JET. But if there is a bug in a third-party API that manifests itself on the Sun JRE, it is unlikely to disappear on another implementation, being it Excelsior JET, Oracle JRockit, or IBM JRE.

    What you can do is:

    • direct your complaints to SWT authors;
    • make the fixes yourself and contribute them back to SWT; or
    • pay someone (e.g. Excelsior) for fixing SWT

  5. Excelsior JET 6.5 came out shortly before the Eclipse 3.5 Galileo release, and thus only supported Eclipse RCP versions 3.1 to 3.4. Therefore we have quickly prepared and issued Maintenance Pack 1, an optional update that adds support for Galileo.

    No customer issues are fixed in MP1, so you only need to download it if you are evaluating or using Excelsior JET for the protection of applications based on the latest version of Eclipse RCP.

  6. I assume building the libxds.a on the x86_64 architecture would help but I need some help to do this.

    No, you need to force the linker to create a 32-bit executable. Figure out the respective gcc command-line parameter and patch the LFLAGS definition in [tt]bin/xc.tem[/tt] under your Native XDS-x86 directory.

    If you succeed, please post your results here for the benefit of others.

  7. There is no mention of Windows Vista? Is Excelsior Jet currently capable of creating a service that can run on Windows Vista?

    Yes, Vista and Windows Server 2003 are supported. The docs are outdated - thanks for spotting it!

    Note: Services compiled with Excelsior JET 6.4 do not run on Windows Server 2008.

    This  issue has been resoved in the forthcoming Excelsior JET 6.5.

    A hotfix for Excelsior JET 6.4 is also available. You may request it from Support Dept. (java at excelsior-usa.com)

  8. Yes, we had thought of this ourselves some time ago, so I have added your feature request to the respective entry in our issue tracker.

    In fact, that entry lists some other options, one of which is already partially implemented. Specifically, it will be possible to create an executable with the java launcher command-line syntax, so you would not only be able to override the hard-wired settings, but also select the main class, e.g.:

        MyApp -Xmx512m -Dsome.property com.myapp.Server
        MyApp com.myapp.Client localhost

    However, due to tight schedule I cannot guarantee that this feature will find its way into the next release.

  9. We have just released Maintenance Pack 1 and the Java SE 6 Update 10 support add-on for Excelsior JET 6.4.

    Among the improvements in Java SE 6u10, formerly known as "Update N" and "Consumer JRE", are a new Swing look & feel called Nimbus and a fully hardware accelerated Windows graphics pipeline. As Excelsior JET includes the Java SE API implementation licensed from Sun, these improvements are now available to our customers.

    We plan to have the Java SE 6 Update 11 support add-on available in January 2009.

  10. Try the following:

    1. Rename that file ([tt]/usr/local/xds/wrk/xc.red[/tt]) to something like [tt]xc.red.saved[/tt]

    2. Run the compiler using the full pathname:

    [tt]/usr/local/xds/bin/xc hello.mod[/tt]

    if this helps, review the content of [tt]xc.red.saved[/tt]. It likely contains incorrect paths, in particular to the directory with symbol files.