Win a copy of Svelte and Sapper in Action this week in the JavaScript forum!
  • Post Reply Bookmark Topic Watch Topic
  • New Topic
programming forums Java Mobile Certification Databases Caching Books Engineering Micro Controllers OS Languages Paradigms IDEs Build Tools Frameworks Application Servers Open Source This Site Careers Other all forums
this forum made possible by our volunteer staff, including ...
Marshals:
  • Campbell Ritchie
  • Ron McLeod
  • Paul Clapham
  • Bear Bibeault
  • Junilu Lacar
Sheriffs:
  • Jeanne Boyarsky
  • Tim Cooke
  • Henry Wong
Saloon Keepers:
  • Tim Moores
  • Stephan van Hulst
  • Tim Holloway
  • salvin francis
  • Frits Walraven
Bartenders:
  • Scott Selikoff
  • Piet Souris
  • Carey Brown

The Java Module System : Challenges and Advantages

 
Ranch Hand
Posts: 163
Netbeans IDE Tomcat Server Java
  • Mark post as helpful
  • send pies
  • Quote
  • Report post to moderator
Hi Nicolai,

What are the major challenges and advantages faced while adopting the module system method compared to the previous systems ?
 
Saloon Keeper
Posts: 6594
161
Android Mac OS X Firefox Browser VI Editor Tomcat Server Safari
  • Mark post as helpful
  • send pies
  • Quote
  • Report post to moderator

compared to the previous systems ?


Which previous systems do you mean, specifically?
 
Greenhorn
Posts: 17
6
  • Mark post as helpful
  • send pies
  • Quote
  • Report post to moderator
I'm also not sure what you mean by "previous systems" (OSGi maybe?), but I can tell you about the challenges and advantages of "module system" over "no modue system".

Regarding the challenges, there are two sets of those:

  • migrating from Java 8 tü Java 9+
  • turning your code into modules


  • The first step is heavily impacted by the module system and you need to know a little bit about it, but it doesn't come from adding modules. It comes from taking your existing Java-8-application and making it work on Java 9+. This step isn't optional and while you can work on it in increments, getting half the way to your goal gets you nothing - you can't be "Java 8.5"-compatible. ;) See my Java 11 migration guide for details on what to expect. Summary:

  • removal of Java EE modules
  • illegal access to internal APIs
  • removal of deprecated APIs and JavaFX
  • casting to URLClassLoader
  • split packages
  • new version strings


  • The second step, taking your Java 9+ application and turning it into modules, can be done incrementally. You can have half your JARs be modules and will reap about half the benefits (I don't have a good source at hand that explains this succinctly). Regarding the benefits, have a look at this thread.


     
    Divya Shiv
    Ranch Hand
    Posts: 163
    Netbeans IDE Tomcat Server Java
    • Mark post as helpful
    • send pies
    • Quote
    • Report post to moderator
    Thank you Nicolai for the explanation and link. (Previous systems I meant  as no-module system).
     
    security forum advocate
    Posts: 220
    1
    Android Flex Google App Engine
    • Mark post as helpful
    • send pies
    • Quote
    • Report post to moderator
    Thanks for the link. Very detailed and very well organized.
     
    rubbery bacon. rubbery tiny ad:
    Thread Boost feature
    https://coderanch.com/t/674455/Thread-Boost-feature
      Bookmark Topic Watch Topic
    • New Topic