[jboss-jira] [JBoss JIRA] Resolved: (EJBTHREE-2045) Allow singleton container to introduce new metadata bridges for concurrency management

jaikiran pai (JIRA) jira-events at lists.jboss.org
Tue Mar 16 08:00:38 EDT 2010


     [ https://jira.jboss.org/jira/browse/EJBTHREE-2045?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

jaikiran pai resolved EJBTHREE-2045.
------------------------------------

                  Resolution: Done
    Component Fix Version(s): jboss-ejb3-core:1.2.4


> Allow singleton container to introduce new metadata bridges for concurrency management
> --------------------------------------------------------------------------------------
>
>                 Key: EJBTHREE-2045
>                 URL: https://jira.jboss.org/jira/browse/EJBTHREE-2045
>             Project: EJB 3.0
>          Issue Type: Task
>          Components: core
>            Reporter: jaikiran pai
>            Assignee: jaikiran pai
>             Fix For: EJB3_1 1.0.6
>
>
> Currently the metadata bridges are setup within the BeanContainer (BeanContainer.initialize). This makes it impossible to add new metadata bridges (ex: for singleton container concurrency management). 
> Instead of hardcoding the metadata bridges within the BeanContainer, it would be more flexible to allow the EJBContainer to return the AnnotationRepositoryToMetadata with appropriate metadata bridges setup. This way the common metadata bridge setup can be done within EJBContainer and any additional metadata bridges can then be setup through overridden method in individual containers. The BeanContainer while initializing the advisor can then just ask the EJBContainer for the AnnotationRepositoryToMetadata.

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

        



More information about the jboss-jira mailing list