[jboss-jira] [JBoss JIRA] Resolved: (JBAS-8380) Deploy the timerservice-mk2 jar only when there's a EJB3.x deployment in the server

Shelly McGowan (JIRA) jira-events at lists.jboss.org
Fri Sep 24 09:41:29 EDT 2010


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

Shelly McGowan resolved JBAS-8380.
----------------------------------

    Fix Version/s:  6.0.0.M5
                       (was: 6.0.0.CR1)
       Resolution: Done


> Deploy the timerservice-mk2 jar only when there's a EJB3.x deployment in the server
> -----------------------------------------------------------------------------------
>
>                 Key: JBAS-8380
>                 URL: https://jira.jboss.org/browse/JBAS-8380
>             Project: JBoss Application Server
>          Issue Type: Task
>      Security Level: Public(Everyone can see) 
>          Components: EJB3
>            Reporter: jaikiran pai
>            Assignee: jaikiran pai
>             Fix For:  6.0.0.M5
>
>
> The EJB3 timerservice-mk2.jar is only applicable for EJB3.x beans. So if there are no EJB3.x deployments in the server, then there's no point in deploying that timerservice-mk2.jar. Deploying that jar on-demand (i.e. when the first EJB3.x deployment becomes available) is also going to improve the AS boot time.
> The referenced forum thread has more details.

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

        


More information about the jboss-jira mailing list