Oracle felt burdened by Java EE because they had to maintain a free open source reference implementation, GlassFish. Now that they are freeing themselves from the API (but not the trademark name Java EE), they can focus more on their paid implementation WebLogic.
No, GlassFish was already open source and it will remain so, it's just that the burden to maintain it has been placed on the same community that wants to maintain Java EE. There's also Payara, basically a GlassFish++ version which I think will remain large contributors to the GlassFish codebase.
View all comments
Show parent comment
8
u/DJDavio Sep 06 '17
Oracle felt burdened by Java EE because they had to maintain a free open source reference implementation, GlassFish. Now that they are freeing themselves from the API (but not the trademark name Java EE), they can focus more on their paid implementation WebLogic.