[jbossseam-issues] [JBoss JIRA] Commented: (JBSEAM-1844) @Raise event does not work with @Observer in the same bean
Jesse Sweetland (JIRA)
jira-events at lists.jboss.org
Tue Jul 8 22:50:26 EDT 2008
[ http://jira.jboss.com/jira/browse/JBSEAM-1844?page=comments#action_12420501 ]
Jesse Sweetland commented on JBSEAM-1844:
-----------------------------------------
I am having a similar issue. In my case, I have two SFSBs. A method is invoked on the first, which outjects an object that is injected into the second, and starts a nested conversation. A method on the second raises an event using Events.instance().raiseEvent, with an argument, which is then picked up by a method on the first SFSB that is annotated with @Observer. After the @Observer method fires, the first SFSB component is cleared from the conversation context. By that I mean when I go to debug.seam the first SFSB component is initially listed in the conversation context, but when I click on it the page refreshes and instead of seeing the details of that bean I see all of the conversations and scopes and the first SFSB component is no longer listed. Neither the @Destroy nor the @Remove method is ever invoked. Both beans are in conversation scope. Setting create=false on the @Observer annotation does not have any effect. Putting the first bean in session scope resolves the issue.
> @Raise event does not work with @Observer in the same bean
> ----------------------------------------------------------
>
> Key: JBSEAM-1844
> URL: http://jira.jboss.com/jira/browse/JBSEAM-1844
> Project: Seam
> Issue Type: Bug
> Components: Core
> Reporter: Ilya Doe
> Priority: Minor
> Fix For: The future
>
>
> If the method that is annotated with @RaiseEvent is in the same stateful bean (conversation scoped) with the method annotated @Observer; when the observer method is called all to-be injected fields are null.
> See details in the forum post:
> http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4074789
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators: http://jira.jboss.com/jira/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira
More information about the seam-issues
mailing list