[jboss-jira] [JBoss JIRA] Updated: (EJBTHREE-1623) Bind EJB3 Registrar in @Start callback of MC Bean, not upon every deployment in EJB3 Deployer

[Andrew Lee Rubinger (JIRA)]

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

Andrew Lee Rubinger updated EJBTHREE-1623:
------------------------------------------

    Fix Version/s: 1.0.0-CR2
                       (was: 1.0.0-CR1)


> Bind EJB3 Registrar in @Start callback of MC Bean, not upon every deployment in EJB3 Deployer
> ---------------------------------------------------------------------------------------------
>
>                 Key: EJBTHREE-1623
>                 URL: https://jira.jboss.org/jira/browse/EJBTHREE-1623
>             Project: EJB 3.0
>          Issue Type: Task
>          Components: common
>            Reporter: Andrew Lee Rubinger
>            Assignee: Andrew Lee Rubinger
>             Fix For: 1.0.0-CR2
>
>
> The EJB3 Registrar (MC) is bound to the locator upon the first eligible EJB3 Deployment.  This registration should be done by passing the Kernel to the constructor of an MC Bean, and placing this in service.  Other services then requiring the EJB3 Registrar may depend upon this bean.

-- 
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