Jump to content
Excelsior Forums
Sign in to follow this  

Brand-new deployment model for Java SE applications

Recommended Posts

Among other improvements in the upcoming version 5.0 of Excelsior JET, we plan to introduce a new deployment technique that will help you further reduce the download size of your Java apps.

The key idea is to select a few components of the entire Java SE API, which the developers could optionally exclude from the installation if the application does not use them.

For example, if your application does not use any of AWT, Swing, CORBA or, say, JNDI API, you will be able to exclude them from the installation created with the JetPackII tool.

To comply with the Java Compatibility requirements, the excluded components should be placed on a Web server to which the deployed application has access for downloading the components at run time.

NOTE: the actual download from the server will occur if and only if your application tries to use any of the excluded components.

With this technique enabled, JetPackII will create two packages:

- the installer to be shipped to end users; and

- a downloadable bundle (single file) to be placed on the server

JetPackII will also hard-wire the URL of the bundle into the application?s executable so that the JET Runtime will get access to the bundle, if necessary.

No changes to the application source code are required to use this deployment model.

Please share your comments or questions about this new technique, e.g. by replying to this message. Your feedback is very welcome.

We also would like to test this deployment model on your Java applications before the first beta of Excelsior JET 5.0 appears. If you think that your application will benefit from ?trimming the baggage?, and you don?t mind us using it for testing, please drop us a line and our engineers will contact you.

Share this post

Link to post
Share on other sites
Sign in to follow this