[
https://issues.apache.org/jira/browse/MYFACES-2396?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12779553#action_12779553
]
Jakob Korherr commented on MYFACES-2396:
----------------------------------------
I also thought about that. The only thing, which I did not like about it, is
that the StartupServletContextListener would also be a HttpSessionListener,
RequestListener,.... and so he does more than his name
"StartupServletContextListener" tells us. But I suppose this is better than the
registration of a second Listener. I'll change the patch!
> @PreDestroy method of Bean in CustomScope not invoked
> -----------------------------------------------------
>
> Key: MYFACES-2396
> URL: https://issues.apache.org/jira/browse/MYFACES-2396
> Project: MyFaces Core
> Issue Type: Bug
> Components: JSR-314
> Affects Versions: 2.0.0-alpha
> Reporter: Jakob Korherr
> Attachments: myfaces_2396_proposal.patch
>
>
> Testing the mojarra 2.0.1 sample "custom-bean-scope", MyFaces does NOT behave
> like Mojarra.
> The problem is that MyFaces does not propagate a PreDestroyCustomScopeEvent
> correctly. The following code is from the mojarra sample and shows how the
> event is published:
> public void notifyDestroy() {
> // notify interested parties that this scope is being
> // destroyed
> ScopeContext scopeContext = new ScopeContext(SCOPE_NAME, this);
> application.publishEvent(FacesContext.getCurrentInstance(),
> PreDestroyCustomScopeEvent.class, scopeContext);
> }
> However, the @PreDestroy method of the Bean, which is stored in the scope, is
> not invoked.
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
