Vitaly Mikheev |
June 23rd, 2009 |
Excelsior JET is a compliant Java SE JVM (yes, it has passed the awesome huge JCK testsuite).
Today news: Excelsior JET 6.5 supports the core of Eclipse Runtime (Equinox OSGi) at the JVM level. Specifically, wiring OSGi bundles, consistency checking before execution and lazy activation of OSGi bundles are supported.
What are the benefits of deploying applications with the JVM that serves as an OSGi container?
As Excelsior JET supports ahead-of-time compilation, the developers of commercial Eclipse RCP and Equinox applications benefit from the ultimate code obfuscation and protection of sensitive data: the applications can be compiled down to native code executables and distributed without the original jar files. Java decompilers are left at bay.
Moreover, merging Java and Equinox Runtimes results in the most secure environment for running Eclipse RCP applications. The environment blocks tampering with OSGi bundles and injecting unauthorized code via Java classloading hooks by protecting the Eclipse Runtime itself.
Finally, the consistency of Eclipse RCP applications can be checked statically to prevent run-time errors.
Flash demo, customers’ success stories, sample RCP applications compiled to native code (including the Eclipse IDE) and fully functional trial downloads are available here.
Official press-release
Excelsior JET home page
P.S. This new version of Excelsior JET is mostly focused on Eclipse RCP. However, the implemented Java Runtime technology can be used in other areas where OSGi shines, e.g. for Spring DM. We would greatly appreciate your feedback on this topic.
Categories: Eclipse RCP, Excelsior JET, Java
Tags: eclipse, Java, osgi, rcp
Dmitry Leskov |
August 28th, 2008 |
Update 09-Dec-2008: We have released the Java SE 6 Update 10 support add-on for Excelsior JET 6.4.
Update 13-Oct-2008: Thanks to everyone who responded by email or in the comments below. Sun has postponed its release, so we had no choice but to concentrate on beta 2. But now we know that Java SE 6 Update 10 support is very important for a number of our customers, and will start working on the respective Excelsior JET add-on as soon as 6u10 becomes generally available.
We are seeking input from Excelsior JET users to help us prioritize our engineering efforts for the next few weeks. Specifically, we need to know your plans for moving to Java SE 6 Update 10, and here is why:
As you may know, Sun Microsystems is about to release Java SE 6 Update 10 (formerly known as “Update N” and “Consumer JRE”). They describe it as “an update release that introduces new features and enhancements aimed at providing an optimized consumer end user experience.”
Among other improvements are fully hardware accelerated graphics pipeline (Windows-only) and a new Swing look & feel called Nimbus. As the Java SE API implementation in Excelsior JET Runtime is licensed from Sun, these improvements will be available to our product users as soon as we publish the respective add-on.
Now, we could start working on that add-on as soon as Sun releases Java SE 6u10, putting Excelsior JET 6.5 development aside. Or we could continue 6.5 development until reaching the Beta 2 milestone, scheduled to Sep 15. Problem is, two key developers were going to take vacations after that milestone, so the add-on release would be delayed for a few weeks in this case.
That said, would you please let us know if you need to move to Java SE 6u10 ASAP? You can do that by posting a comment below or dropping a line to java at excelsior-usa.com.
Categories: Excelsior JET, Java
Tags: Java
