On Mon, Jan 18, 2016 at 6:21 PM, Adam Bien <abien_at_adam-bien.com> wrote:
> …and all of my customers who using appservers also using EJBs. EJBs are
> perfect for microservices. Monitoring and throttling are built-in and the
> performance is really good :-)
>
From a practical point of view there's little wrong with EJBs themselves
these days. If you read the ZEEF article on Adam's blog you'll see that
ZEEF uses EJBs too (a lot really).
But from a Java EE architecturally/coherency point of view I think we
should strive to move as many unique EJB services as we can to CDI, since 2
component models are simply confusing, even when the models individually
are not "wrong".
My 2 cents ;)
>
> cheers,
>
> adam
> >
> > Antonio
> >
> > Le 18 janv. 2016 16:34, "Abhishek Gupta" <abhirockzz_at_gmail.com> a écrit
> :
> > Definitely +1. Good to see some EJB related discussions :-)
> >
> > The above mentioned annotations would help
> >
> > 1. Tune EJBs in a standard manner
> > 2. Sending across a clear message w.r.t one of the most important EJB
> features e.g. @Stateless does not really say that you also have throtlling
> & pooling capabilities (one needs to mention it explicitly)
> >
> > I also suggest including another annotation: @javax.ejb.InitialPoolSize.
> This will aid in eager initialisation (just like Singleton EJBs) and ensure
> having enough firepower 'in the tank' to begin with
> >
> > Thanks
> > Abhishek
> >
> > Thanks
> >
> > Abhishek
> > ------------------------------------------------------------------------
> > Latest (mini) book ! | Java Caching Refcard | Java EE Blog
> >
> >
> >
> >
> > On Mon, Jan 18, 2016 at 1:36 PM, arjan tijms <arjan.tijms_at_gmail.com>
> wrote:
> > +1
> >
> > Pool settings as well as an @TransactionTimeout would be quite handy
> indeed.
> >
> > On Mon, Jan 18, 2016 at 8:58 AM, <johan_at_lodgon.com> wrote:
> > +1
> >
> > This really can save lots of boilerplate code in projects.
> >
> >
>
> workshops.adam-bien.com
> effectivejavaee.com
> blog.adam-bien.com
> airhacks.news
>
> Author of:
> "Real World Java EE Night Hacks”,
> "Real World Java EE Patterns— Rethinking Best Practices"
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>