We've been making significant improvements to JExpress starting with version 7.1.3. Existing JExpress customers must uninstall any JExpress 7.1.2 or earlier version, and install the latest release because program names and the file layout have changed. Also, there is a new url for downloading updates so the Update JExpress Professional menu/script will not work until you install the latest version.

All of your existing JExpress project files *will* continue to work *without* any changes. There are some enhancements that you could make to get the most out of the new JExpress. If you build installers unattended, then read this. And, if you distribute a different version of the JRE than 1.4, then changes to the platform properties.

Program and Class Name Changes

• JExpress Professional -> JExpress
• JExpressBuilder -> JExpress
• JExpressDeveloper -> JExpress
• Update JExpress Professional -> JExpress
• JUpdate.class -> JExpressUpdater.class
• JUninstall.class -> JExpressUninstaller.class
• JExpressLoader -> eliminated

Build Directory

• The platforms subdirectory tree has been replaced by the installers subdirectory.
• The filenames for the installers have changed. Each installer includes the product name, version, and OS.
• The build directory now contains index.html that lets your customers have 1 page to download any installers created. download.html lists the various installers, file size, and minimum JRE requirements. Learn more about the web pages.

Unattended Builds

• Unattended builds must use com.denova.JExpress.Build.JExpressAdvanced instead of com.denova.JExpress.Build.JExpressDeveloper class.

Custom Classes

• Custom classes for the installer can be stored in a directory specified on the Custom tab. If a directory is not specified, then the custom classes must be in the JExpressInstaller subdirectory.
• Custom classes for the uninstaller can be stored in a directory specified on the Custom tab. If a directory is not specified, then the custom classes must be in the CustomUninstaller subdirectory.
• Custom classes for the updater can be stored in a directory specified in the dialog box for the Updater's custom classes. If a directory is not specified, then the custom classes must be in the JExpressUpdater subdirectory.
• The constructor no longer needs to pass the errorLog. Custom classes that pass the errorLog continue to work, but the errorLog variable is superseded by the new ErrorLog class.
• You can probably simplify your custom classes by using enter() and leave() methods in the WizardPanel instead of setActive(boolean active). The code that was guarded inside if (active) should be moved to enter() and code that was in the else should be inside the leave() method. This is not required, but it probably will make your custom classes clearer.

Web Pages

• Simplified the web pages generated for the installers so now there is an index.html, download.html, and howto subdirectory.
• download.html is a fragment of html that contains the file size and JRE requirement for each installer and can be included in a customized page.
• The howto subdirectory contains additional details about installing the various types of installers.
• The JExpressBase subdirectory has been renamed to "webpages".
• If you prefer that the download webpage look like the rest of your website, then you can create a wrapper around download.html. You can see any example of a basic wrapper here.
• You can change the webpages/index.html if you'd like, but future updates may overwrite any changes. It is probably better to create your own file as a wrapper to the pre-configured html that JExpress generates.
• It's strongly recommended that you not change index.html and download.html because JExpress relies on the format to make changes during the build.

Platform Properties

• The loaderJavaCommand, loaderClasspath, and installerExecutable values have changed in the platform.properties files. If you changed the version of the jvm you ship or added jar files to the classpath, then you should apply the same changes to the new platform.properties files.
• You can now create a jvm distribution file using the Advanced interface for JExpress. Simply click the Create button OS' subtab on the JVM tab.

Directory Restructure

• JExpress default installation directory is JExpress instead of JExpressProfessional.
• JExpressLoader subdirectory and program have been eliminated.
• You should no longer use the JExpressInstaller or JExpressUpdater subdirectories to store your custom classes.
• JExpressBase directory is now called webpages.