As Oracle axes support for GlassFish, MySQL users might want to pay attention

Re:As Oracle axes support for GlassFish, MySQL users might w... by pron on Friday November 15, 2013 @11:44AM (#6740398)

The concerns over MySQL might be justified, but have little to do with GlassFish. GlassFish has never been a popular open source project like Tomcat, Jetty or JBoss, and probably not as commercially successful as Oracle's own WebLogic, or IBM's WebSphere, or JBoss. There was really no good reason to keep it alive, other than as the JEE reference implementation, a role which, as I understand, it will continue to serve.

Also, the compatibility between different Java EE application servers is far greater than between different DBs, and migrating from one to the other is usually very simple.

I do hope (and would like to assume) that only the work on the GlassFish server will be reduced, while popular subprojects like Jersey[1] will continue as before.

[1]: https://jersey.java.net/

[ Parent | on HN ]

Re:As Oracle axes support for GlassFish, MySQL users might w... by batbomb on Friday November 15, 2013 @01:17PM (#6741060)

Jersey is an integral part of WebLogic as well, so development will assuredly continue.

From the jersey mailing list:

> Jersey remains the JAX-RS implementation in WebLogic as well as JAX-RS RI in GlassFish. The decision to not provide a commercial GF 4.x offering is orthogonal to Jersey and JAX-RS development.

> ...and now, just to be safe, I should probably add the standard Oracle disclamer :) Here it goes:

> The preceding is intended to outline our general product direction. It is intended for information purposes only, and may not be incorporated into any contract. It is not a commitment to deliver any material, code, or functionality, and should not be relied upon in making purchasing decisions. The development, release, and timing of any features or functionality described for Oracle’s products remains at the sole discretion of Oracle.

> Marek

[ Parent | on HN ]