Mailing-List: contact users-help@openejb.apache.org; run by ezmlm
Precedence: bulk
Reply-To: users@openejb.apache.org
Received-SPF: pass (athena.apache.org: domain of david.blevins@gmail.com
 designates 209.85.160.48 as permitted sender)
Content-Type: text/plain; charset=us-ascii
Mime-Version: 1.0 (Apple Message framework v1251.1)
Subject: Re: Jetty Support
From: David Blevins <david.blevins@gmail.com>
In-Reply-To: <1327918411194-4340539.post@n4.nabble.com>
Date: Mon, 30 Jan 2012 09:39:48 -0800
Content-Transfer-Encoding: quoted-printable
Message-Id: <F29AB25B-0B67-4050-93B5-8A7C05AF9876@gmail.com>
References: <1327910443608-4340294.post@n4.nabble.com>
 <CACLE=7OM+LZ6ZCHvF=9eaZrTr_hw_56WuDHRm7i4GcTqZZ4pSQ@mail.gmail.com>
 <1327918411194-4340539.post@n4.nabble.com>
To: users@openejb.apache.org


On Jan 30, 2012, at 2:13 AM, john70 wrote:

> Hi Romain,
>=20
> Thank you very much for response!
>=20
>=20
> Romain Manni-Bucau wrote
>>=20
>> Why do you prefer jetty? You can run tomee in a test, you can use
>> arquillian, you can run it from your pom too. Do you prefer jetty =
because
>> of jetty or because of something missing to tomcat/tomee?
>>=20
>=20
> First because of Jetty and second because Jetty has full and rock =
solid
> support for WebSockets protocol. I know that JEE7 will add WebSockets
> support later this year to the Servlet specification. But for me it is =
not
> clear when Tomcat will add support for WebSockets. And if Tomcat =
developers
> add support for WebSockets, they will need time to make it bug-free =
and rock
> solid. And Jetty developers (especially Greg Wilkins) have =
participated in
> the development process of WebSockets protocol and have a working
> implementation for at least one year.
>=20
> Currently we are using JBoss 4.2 with Jetty and it works very well. =
But
> JBoss 4.2 is really old and we would like to replace it with something =
new.
> We are looking currently at all application servers and one option =
was/is to
> use Jetty with OpenEJB. But if you don't have support for Jetty or do =
not
> plan to add support for Jetty, than we can remove OpenEJB from out
> candidates list.

The big question is if you need it to be Java EE 6 certified.  Restoring =
the Jetty module is fairly easy, Java EE 6 certifying it would take a =
couple months.


-David