[
https://issues.apache.org/jira/browse/MYFACES-2509?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12844406#action_12844406
]
Jan-Kees van Andel edited comment on MYFACES-2509 at 3/12/10 7:57 AM:
----------------------------------------------------------------------
I think you're right.
I initially only considered it to be used for startup listeners, and I don't
think those classes should contain state, but on the other hand, we shouldn't
have such a silent, undocumented requirement. This will indeed cause weird bugs.
was (Author: jankeesvanandel):
I think you're right.
I initially only considered it to be used for startup listeners, and I don't
think those classes should contain state, but on the other hand, we shouldn't
have such a silend, undocumented requirement. This will indeed cause weird bugs.
> @ListenerFor not processed for global system events
> ---------------------------------------------------
>
> Key: MYFACES-2509
> URL: https://issues.apache.org/jira/browse/MYFACES-2509
> Project: MyFaces Core
> Issue Type: New Feature
> Components: JSR-314
> Affects Versions: 2.0.0-alpha
> Reporter: Jan-Kees van Andel
> Assignee: Jan-Kees van Andel
> Attachments: ListenerFor_support.patch
>
>
> We currently don't process @ListenerFor and @ListenerFor annotations on
> non-component types.
> This is specified in the spec for global system events, see:
> http://java.sun.com/javaee/javaserverfaces/2.0/docs/api/index.html?javax/faces/event/ListenerFor.html
> It would be nice to have it in the beta.
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
