Mailing-List: contact users-help@openejb.apache.org; run by ezmlm
Precedence: bulk
Reply-To: users@openejb.apache.org
Received-SPF: softfail (athena.apache.org: transitioning domain of
 johndoe70@mail.ru does not designate 216.139.236.26 as permitted sender)
Date: Tue, 31 Jan 2012 00:12:50 -0800 (PST)
From: john70 <johndoe70@mail.ru>
To: users@openejb.apache.org
Message-ID: <1327997570812-4343805.post@n4.nabble.com>
In-Reply-To: <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>
 <F29AB25B-0B67-4050-93B5-8A7C05AF9876@gmail.com>
Subject: Re: Jetty Support
MIME-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Transfer-Encoding: 7bit

Hi David,


David Blevins-2 wrote
> 
> 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.
> 

Does it really matter whether it is certified or not?
I mean, my customers does not care whether we run our product on a certified
or on a not certified application server. What matter for my customers is
stability and high performance. For me personally it is important, that the
application server consumes as less resources as possible. What also
important for me is the support for following technologies:
- JCA 1.6
- JTA 1.1 with full XA support
- JMS provided by a resource adapter (we have already an established network
of MQ servers)
- EJB 3.1
- JPA2 provided by Hibernate (we need Hibernate as we use Hibernate Search
in our product)
- JavaMail

Best regards,
John


--
View this message in context: http://openejb.979440.n4.nabble.com/Jetty-Support-tp4340294p4343805.html
Sent from the OpenEJB User mailing list archive at Nabble.com.