Path: csiph.com!aioe.org!.POSTED!not-for-mail
From: =?UTF-8?Q?Arne_Vajh=c3=b8j?= <arne@vajhoej.dk>
Newsgroups: comp.lang.java.programmer
Subject: Re: JDK 11 will loose some weight
Date: Wed, 24 Jan 2018 20:55:13 -0500
Organization: Aioe.org NNTP Server
Lines: 28
Message-ID: <p4bddv$i6p$1@gioia.aioe.org>
References: <70d51397-d130-4a50-b1ed-b685bf51cad9@googlegroups.com>
NNTP-Posting-Host: PBuS014lhzVyHjLbXmo/ZQ.user.gioia.aioe.org
Mime-Version: 1.0
Content-Type: text/plain; charset=utf-8; format=flowed
Content-Transfer-Encoding: 7bit
X-Complaints-To: abuse@aioe.org
User-Agent: Mozilla/5.0 (Windows NT 6.1; WOW64; rv:52.0) Gecko/20100101 Thunderbird/52.5.2
Content-Language: en-US
X-Notice: Filtered by postfilter v. 0.8.2
Xref: csiph.com comp.lang.java.programmer:37994

On 1/22/2018 7:43 PM, bursejan@gmail.com wrote:
> JEP 320: Remove the Java EE and CORBA Modules
> http://openjdk.java.net/jeps/320
> 
> JDK 11: End of the road for Java EE modules
> https://jaxenter.com/jdk-11-java-ee-modules-140674.html

I must admit that I don't get it.

Some things are fine:
* CORBA out - no problem, practically nobody has used that the last 15 years
* JTA out - no problem, if you have a transaction manager then you are 
in Java EE world
* WS server side out - no problem, if you serve HTTP requests then you 
are in the Java EE world

But other things are not fine:
* JAXB out - problem, it is perfectly valid to use JAXB in Java SE 
applications
* WS client side out - problem, it is perfectly valid to call web 
services from Java SE applications

Arne