[
Date Prev][
Date Next][
Thread Prev][
Thread Next][
Date Index][
Thread Index]
[
List Home]
|
Re: [jakartaee-platform-dev] VOTE: Specifications to add inJakartaEE 9
|
--
Jason Greene
Distinguished Engineer & Manager
Red Hat, Inc.
> On Nov 27, 2019, at 1:32 PM, Erik Brangs <erik.brangs@xxxxxx> wrote:
>
> Hi,
>
> On 27.11.2019 19:21, Werner Keil wrote:
>> Well it breaks as soon as they run their Java EE 8 compliant app or container in a JDK above Java SE 9, so it is not the fault of Java EE or Jakarta EE in that case.
>
> To me, it does not matter whose fault it is. What matters to me is that it breaks my expectations. I think that not providing technologies that were available in Java EE 8 (even if they came from Java SE) is very risky for the future of the project because it runs contrary to the expectations of backwards compatibility that might exist. In my opinion, backwards compatibility is essential and in the special case of Jakarta EE it is not only about what's actually in the specs but also about the perception of changes by the community.
Not bringing in JAXB is actually the better outcome in terms of compatibility, since we will end up with 1 JAXB instead of the 2 it would create bringing it over, and no code changes will be required to use it (since the package names stay the same, vs it was brought over existing applications would have to change to use it). My guess is most venders will still ship the original JAXB, but for those that don’t adding is one simple step of adding it to the deployment or to the runtime’s global classpath. A step that is much less work than dealing with package renames and the fact that now JAX-WS uses a different JAXB than the one in the platform.
-Jason
