As mentioned earlier, for "long term", I want something outside of the
JavaEE range anyways:
* Server based on Netty + Netty JAX-RS plugin
* Async DB access
But given our goal to release soemthing _early_ August, why not doing
This one is not that hard to write, and will help to get feedback on our
software (and the concepts behind).
With that feedback, we can improve from there
On Tue, May 28, 2013 at 7:52 AM, Matthias Wessendorf <matzew(a)apache.org>wrote:
On Tue, May 28, 2013 at 6:07 AM, Douglas Campos <qmx(a)qmx.me> wrote:
> On Mon, May 27, 2013 at 06:44:43PM +0200, Matthias Wessendorf wrote:
> > On Mon, May 27, 2013 at 5:51 PM, Sebastien Blanc <scm.blanc(a)gmail.com
> > > Maybe I'm totally wrong but using EJB on a plain old Tomcat/Jetty
> will be
> > > the same issue as using JMS, no ? (Or by Tomcat when meant TomEE ? )
> > JMS integration is a bit harder (separated broker), compared to
> > an embedded EJB container (e.g. Apache OpenEJB).
> > I have always thought that we do target - first - the WebProfile of
> > 6 (which contains EJB, but not JMS)
> I think the question is: can't we avoid **both** JMS and EJB/CDI? I'm
> probably missing something, but for me I can't see the reason beyond
> just using it for the sake of it...
like using plain JDBC and handwritten factories, instead of JPA/EJB/CDI ?
> aerogear-dev mailing list