Talk:Modular Java SE

Would it be a compatible change to introduce a new interface, which Applet implements (for discussion purposes, let's call it IApplet), and change the signature of AppletInitializer to take IApplet instead of Applet?

--Rich Unger 01:57, 16 June 2009 (CEST)

Hello Rich, thanks for your note. To make things better, the IApplet would have to be defined in java.beans module. Moreover it would not be compatible to change the method signature in AppletInitializer, there would have to be new AppletInitializer2 that would take IApplet. This could work, but I am horrified: I've just found out that there is a static method in Beans class that takes AppletInitializer as an argument. That is unexpected complication.

--JaroslavTulach 14:22, 16 June 2009 (UTC)

You create a humungeous dataset based on an Architectural Description Modelling Language (ADML) that captures the dependencies of every component. Then you set to work to tease apart the interdependencies so that you have some clearly deliniated system components.

Start now and you should have a good result in a couple of years. It'll need full time work, at least to marshall the components into an overall system model.

If you think I'm speaking from experience, you're right.

--mel pullen 00:17, 17 June 2009 (CEST)

Nice outlook. I should correct my expectations then! I need result in half a year and moreover I need to keep BackwardCompatibility - e.g. not only tear things apart but do it in a way that when composed together everything will look like it used to!

--JaroslavTulach 11:54, 17 June 2009 (UTC)

You are doing a great job! I can't wait to lay my hands on modular JDK! (unfortunately I was not able to build JDK myself as you described)

--Ivan 13:22, 26 June 2009 (CEST)

If you are interested, then let's improve the instructions on how to build the system. Can you build the monolithic OpenJDK using its original make files?

--JaroslavTulach 12:15, 26 June 2009 (UTC)