Iâd like to see the reference implementation (GlassFish) tackle the name spacing first. How hard will it be for GlassFish to support both EE 8 and EE 9 (assuming 9 has a different namespace)? To me this debate has been somewhat abstract. The impact of the refactoring is going to depend upon application complexity. Some organizations are deploying multiple applications to containers (which by different groups on different schedules) which communicate via RMI etc.
This is one point of confusion not specific to this conversation, but GlassFish is not the reference implementation for Jakarta EE.Â There is no RI in Jakarta EE instead at least one vendor has to demonstrate compliance before a platform is approved.Â
Separately, I think the Java ecosystem is going through a bit of upheaval at the moment with getting code running on post Java 8. With Java 9, the technical debt bill came due. Do we want to throw a namespace challenge into the mix at the moment when companies are grappling with transitioning to Java 11?
This is a challenge, but we can't stifle innovation in the EE space because the SE space is innovating. We would be waiting forever for things to settle down, if they ever do, in the SE space.
ÂJust curious, why arenât the individual specs making the decision on when they jump to the new namespace?
That would be kind of crazy with some going to Jakarta EE and others sticking with javax?Â ÂAlso, remember that the javax namespace cannot evolve at all, so any active project where innovations are desired would be shooting itself in the foot to stick with the javax namespace.Â It needs to be a platform decision.
> On May 10, 2019, at 3:38 PM, domi <dbuechner93@xxxxxxxxx> wrote:
> I totaly agree with you guys.
> another point why i prefer the BIG-BANG transition is that after that step you can say IT'S DONE and build jakarta ee on a "carefree base".
> Am 10.05.19 um 18:54 schrieb Mark Struberg:
>> And even worse: we would break backward compat with every Jakarta EE release :(
>>> Am 10.05.2019 um 14:33 schrieb David Blevins <dblevins@xxxxxxxxxxxxx>:
>>>> On May 10, 2019, at 8:55 PM, Richard Monson-Haefel <rmonson@xxxxxxxxxxxxx> wrote:
>>>> In the github proposal for Incremental, it says over and over again that the result would be mixed namespaces.Â But the Big Bang never says that yet it does say "Any packages not moved from javax to jakarta could be included in Jakarta EE, but would be forever frozen and never move to the jakarta namespace."Â Âwhich is exactly the same thing, right?
>>> Here's where they're the same:
>>>Â ÂJakarta EE 9 comes out and it is some mix of javax and jakarta.Â You must learn the mix.
>>> Here's where they're different:
>>>Â ÂBig Bang: Jakarta EE 10 comes out.Â You already learned the mix, you're good.
>>>Â ÂIncremental: Jakarta EE 10 comes out.Â Forget the old mix, learn the new one.Â Also update your source code again.
>>> And worse case...
>>>Â ÂBig Bang: Jakarta EE 11 comes out.Â You already learned the mix, you're good.
>>>Â ÂIncremental: Jakarta EE 11 comes out.Â Forget the old mix, learn the new one.Â Hope you have any chance of keeping it straight.Â Hope your boss doesn't get mad when you tell her you have to migrate source again to use a new feature.
>>> jakartaee-platform-dev mailing list
>>> To change your delivery options, retrieve your password, or unsubscribe from this list, visit
>> jakartaee-platform-dev mailing list
>> To change your delivery options, retrieve your password, or unsubscribe from this list, visit
> jakartaee-platform-dev mailing list
> To change your delivery options, retrieve your password, or unsubscribe from this list, visit
jakartaee-platform-dev mailing list
To change your delivery options, retrieve your password, or unsubscribe from this list, visit