[jboss-jira] [JBoss JIRA] Commented: (EJBTHREE-1701) getTimerService() can no longer be called in @Service start()

[Andrew Lee Rubinger (JIRA)]

    [ https://jira.jboss.org/jira/browse/EJBTHREE-1701?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12449981#action_12449981 ] 

Andrew Lee Rubinger commented on EJBTHREE-1701:
-----------------------------------------------

Likely you'll need some help working with the @Service Container lifecycle to get around this.

If you can make my job really easy (ie. attach an integration test and build-test.xml changes in a patch to this issue) it'll really help me give it some more attention.

PS - After some more patches/tests we can get you a CLA and commit rights.

> getTimerService() can no longer be called in @Service start()
> -------------------------------------------------------------
>
>                 Key: EJBTHREE-1701
>                 URL: https://jira.jboss.org/jira/browse/EJBTHREE-1701
>             Project: EJB 3.0
>          Issue Type: Bug
>          Components: core
>    Affects Versions: trunk
>         Environment: 5.0.0.GA
>            Reporter: Matt C
>            Assignee: Andrew Lee Rubinger
>
> Calling getTimerService() is no longer allowed from the lifecycle methods of @Service.
> Exception java.lang.IllegalStateException: getTimerService() not allowed during injection (EJB3 4.5.2).
> This occurs in the start() method of a @Service bean. The effect is to disallow setup of application-wide timers.
> This action is erroneously disallowed based on Table 2 in the EJB3 specification, section 4.5.2 (IMHO).
> Service lifecycle methods are not dependency injection methods, furthermore @Service beans are outside of the EJB3 specification.
> Lifecycle methods of a service should probably be considered business methods, not DI in the context of Table 2. They are in the @Management business interface.
> There is no workaround yet for this backwards incompatible change which breaks apps that set up application-wide timers from Services when they are migrated to 5.0.0.GA. This used to work in 4.2.x.

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