Skip to main content

[ejb-spec issues] [JIRA] Commented: (EJB_SPEC-113) Standardize Pooling and Decouple from EJB Component Model

  • From: "reza_rahman (JIRA)" <jira-no-reply@...>
  • To: issues@...
  • Subject: [ejb-spec issues] [JIRA] Commented: (EJB_SPEC-113) Standardize Pooling and Decouple from EJB Component Model
  • Date: Thu, 3 Oct 2013 17:28:17 +0000 (UTC)
  • Auto-submitted: auto-generated


    [ 
https://java.net/jira/browse/EJB_SPEC-113?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=369268#action_369268
 ] 

reza_rahman commented on EJB_SPEC-113:
--------------------------------------

BTW, this is an idea completely decoupled from anything JMS or JCA really.

> Standardize Pooling and Decouple from EJB Component Model
> ---------------------------------------------------------
>
>                 Key: EJB_SPEC-113
>                 URL: https://java.net/jira/browse/EJB_SPEC-113
>             Project: ejb-spec
>          Issue Type: New Feature
>            Reporter: reza_rahman
>
> Instance pooling is currently a non-standard service provided by default to 
> EJB @Stateless beans implicitly by most containers. As a result, although 
> very useful for scalable, reliable mission critical systems this feature is 
> ill understood and ill used.
> This is a proposal to introduce a new annotation for the container instance 
> pooling feature and simultaneously decoupling it from the EJB component 
> model as a generally useful service for suitable managed beans, including 
> CDI beans.
> The programming model could look something like this:
> @Pooled(minPoolSize="...", maxPoolSize="...", ...)
> public class MyScalableService {
>    ...
> }
> This could be it's own (CDI) bean scope - which would make implementation 
> relatively simple. However, I think it would be useful as a generic 
> declarative service that works with various bean scopes perhaps like the 
> following:
> * Default (dependent) scope - create bean instances, pool them and destroy 
> them as needed.
> * @RequestScoped/@SessionScoped/@ConversationScoped/@ViewScoped - Do the 
> life-cycle callbacks at the beginning and end of 
> requests/sessions/conversations/views, but don't actually discard the 
> instance and pool/reuse them instead.
> * @ApplicationScoped/@Singleton - does not make any semantic sense, but 
> perhaps could work with something like @MaxConcurrency that's simply useful 
> for bandwidth/concurrency throttling and not instance pooling.
> Do let me know if anything needs to be explained further - I am happy to 
> help.
> Please note that these are purely my personal views and certainly not of 
> Oracle's as a company.

-- 
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators: 
https://java.net/jira/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira

        


[ejb-spec issues] [JIRA] Commented: (EJB_SPEC-113) Standardize Pooling and Decouple from EJB Component Model

Bruno Borges (JIRA) 10/03/2013

<Possible follow-up(s)>

[ejb-spec issues] [JIRA] Commented: (EJB_SPEC-113) Standardize Pooling and Decouple from EJB Component Model

reza_rahman (JIRA) 10/03/2013

[ejb-spec issues] [JIRA] Commented: (EJB_SPEC-113) Standardize Pooling and Decouple from EJB Component Model

arjan tijms (JIRA) 10/03/2013

[ejb-spec issues] [JIRA] Commented: (EJB_SPEC-113) Standardize Pooling and Decouple from EJB Component Model

reza_rahman (JIRA) 10/03/2013

[ejb-spec issues] [JIRA] Commented: (EJB_SPEC-113) Standardize Pooling and Decouple from EJB Component Model

reza_rahman (JIRA) 10/06/2013
 
 
Close
loading
Please Confirm
Close