Java 9 through 11 have brought along some very large changes that have really shaken up the industry. Namely, the module system and the removal of the web-start deployment facilities. Also, along with this the move away from Oracle being the primary provider of the JDK has left people wondering how to proceed. We’ve been on the bleeding edge of this change and are now in a position to ease the transition for others. Life beyond Java 8 is great once you know how to proceed.
This training is generally tailored to your needs; for example if you have an application that needs to be re-packaged, we would mix the training with some consultancy; leaving you with a modular app that deployed natively and the knowledge to maintain it. For smaller apps two extra days would be enough, in more complex cases, we’d estimate how long it would take to modularise your application.
Take a look at our TcMenu UIs on github which is packaged for both Windows and MacOS natively. Further, the designer UI is plugin based, and the plugins are actually Java modules loaded dynamically. Dave, who provides this training has been a consultant to Tier 1 investment banks for the last 18 years.
- Duration: 2 days for training + extra for consulting
- Cost: £999 for the first 2 days + consulting costs (special offer!)
- Locations: UK and some EU locations
All prices quoted here are for on site training, exclusive of VAT and do not include travel expenses to your site.
Details for contacting us
- Understanding the changes to JDK and which vendor you should use.
- Depending on above, discussing either OpenJDK or commercial Oracle JDK.
- An overview of the module system.
- The JRE has gone - long live jlink.
- Writing and running our first modular application.
- Module definitions, importing, exporting and requiring.
- What to do with dependencies that are not modular.
- Building an example modular application with Maven (or Gradle).
- Other changes in 9, 10 and 11. Many other new features have been added.
- Packaging the modular example using JLink / JPackager.
- Optional module covering either Java Fx deployment or focusing on your apps deployment.
- Packaging Java apps as an Installer for Windows - you’ll need a Windows PC.
- Packaging Java apps as a DMG for MacOS - you’ll need a Mac.
- If needed, native packaging for Linux can be covered. We’ve not yet had demand for this. Most server side components we deploy on Linux are not natively packaged.
Day 3 onwards
- These additional days would revolve around the requirements to make your application modular, and to package your application into a native format.