users@glassfish.java.net

Re: Migrating from Jboss AS 6

From: John Clingan <john.clingan_at_oracle.com>
Date: Tue, 29 Mar 2011 12:26:03 -0700

Not sure why the iPhone dropped off the subject line, so here is a re-post with comments in-line.

On Mar 28, 2011, at 10:18 PM, forums_at_java.net wrote:

> Hey everyone,
>
> Wondering if anyone had made the change from jboss AS to glassfish? I'm

Yes, lots of people switch from various JBoss versions.

> comfortable in dealing with the tech issues but my interest is more in the
> 'soft' issues. For example: (with respect to the community editions)
>
> 1) How do the communities compare in terms of answering questions and
> putting forward patches? Are minor (or component) updated regulary and
> are easier to get hold of and apply?

Our approaches differ on patches & quality of community releases. GlassFish open source releases go through a full battery of tests before we release bits. This includes Java EE 6 compatibility, performance, unit & functional tests, integration & interoperability, longevity, etc. JBoss reserves that level of testing for commercial builds. Patches get pushed to the trunk, and those get picked up on interim community builds, which happen historically roughly every 6 months, but we don't have a hard 6 month release cycle.

Commercial builds get you support, regular patch releases, and some value- added features.

> 2) Is the roadmap generally adhered to? Do expected releases just get
> dropped?

We do our best to adhere to our roadmap. We've been pretty good at it. Since GlassFish is the Java EE reference implemention, we have to support for the latest standards when they are released. This keeps us pretty true to our roadmap.

> 3) Is in-container testing a solid feature in glassfish?
>
> Red hat have eol'd their first and only 'production ready' JEE6 stack (still
> with serious bugs) and are expecting a rewrite of their core to be
> 'production ready' by June 2011. My confidence is low that the deadline and
> quality will be hit.
>

Pretty good. We're doing more work on our embedded API to enable mavenized testing and to achieve full feature parity.

> I'm migrating an app at the moment from j2ee. So if i'm going to migrate to a
> new JEE spec I'd like to do move once and to a stable JEE6 implementation.
> Deabting whether to spend the time now in migrating to a new app server or
> spend time in the futture migrating to an unreleased and totally rewritten
> jboss implementation.
>

We aim to be helpful on the alias. Hope we can help!

> regards,
>
> a.
>
>
> --
>
> [Message sent by forum member 'adamlau']
>
> View Post: http://forums.java.net/node/786170
>
>