[seam-issues] [JBoss JIRA] Resolved: (SEAMCRON-23) Extension does not follow spec

[Peter Royle (JIRA)]

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

Peter Royle resolved SEAMCRON-23.
---------------------------------

    Resolution: Done


> Extension does not follow spec
> ------------------------------
>
>                 Key: SEAMCRON-23
>                 URL: https://issues.jboss.org/browse/SEAMCRON-23
>             Project: Seam Cron
>          Issue Type: Bug
>            Reporter: Peter Royle
>            Assignee: Peter Royle
>             Fix For: 3.0.0.Alpha1
>
>
> I was using @ApplicationScoped provider implementations, expecting the same instance of the bean to be available for injection during AfterBeanValidation and BeforeShutdown. I found that the injected instances were different, and therefore any initialisation I performaed at startup could not properly be unding on shutdown. This was the main cause of SEAMCRON-15. After further investigation and reading this thread (http://weld-development-discussions.46994.n3.nabble.com/clarification-of-AfterDeploymentValidation-td2258389.html) I realise that I cannot depend on any scopes being active during AfterBeanValidation (this seemed to work in OWB though). Not yet sure what the appropriate way is to do this. I'm getting the feeling that if I'm going to be grabbing providers from the manager, they'll need to be no/default-scoped and cached by the extension.

--
This message is automatically generated by JIRA.
For more information on JIRA, see: http://www.atlassian.com/software/jira