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: *_at_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 <
https://leanpub.com/ejb-annotations-primer> ! | Java
Caching Refcard <
https://dzone.com/refcardz/java-caching> | Java EE Blog
<
https://abhirockzz.wordpress.com/>
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.
>>
>
>