4 ms·
> A server-side product will be able to exclude the desktop GUI API (AWT and Swing). That is very unlikely. If you look at the java.desktop module (where thing
by needusername 11y ago
> A server-side product will be able to exclude the desktop GUI API (AWT and Swing).
That is very unlikely. If you look at the java.desktop module (where things like AWT and Swing are) there are also tons of other things there like Java Beans. A lot of Software requires Java Beans at least indirectly (eg. Spring requires Java Beans). In addition there's the following dependency path.
java.xml.ws -> java.xml.bind -> java.activation -> java.desktop
A server side product is very likely going to require at leat one of these.
The fact of the matter is that the JDK code is simply not modular enough.
- mike_hearn 11y agoThe java.desktop module is going to be a prime candidate for further breakdown, probably after Java 9 I guess. It is huge and ships all 3 widget toolkits when most apps need only one.
- needusername 11y agoWhat's the third one? I'm only aware of AWT and Swing. I though that JavaFX was already in its own modules. Is it really realistic to only use one toolkit when Swing is built on AWT and has AWT base classes? What bothers me more is that things like Java Beans are in java.desktop.
- mike_hearn 11y agoJavaFX is in java.desktop too