[JBoss Seam] - Can I end a conversation programmatically?
by raffaele.camanzo
Hi All,
I'm facing a problem trying to end a conversation programmatically.
The scenario:
We have an application (for a full description refer to my previous post: "Problems with application-like behaviour") with a menu and a tabbed view of the services offered to the users; each tab is a conversation with a given id in order to provide to the user the ability to switch between the opened tabs. A user should be able to ask for a service, make the work and then close the tab and then, after a while, ask again for the same service. When the user asks for the tab to be closed the application should clean up all the data related to; this means that we have to remove the tabs control data and the tab content-specific data (the conversation one).
The tab remotion request is handled in a generic way by a session scoped stateful bean (which handles the application behaviour), it removes the control data and then calls the Manager in order to remove the conversation of the current tab and switch to the conversation of the one focused.
The problem:
In order to clean the conversation data the action related to the tab remotion makes these Seam API calls:
| Manager.instance().endConversation(false);
| Manager.instance().switchConversation(currentTab.getConversationId());
|
I think that this should work because the current conversation when I invoke the Manager is the one I want to remove and I hold the data of the one I want to activate.
The effect:
Unfortunately when the user selects the link related to the conversation I tried to remove, Seam, instead of create a brand new conversation with the given identifier, resumes the old conversation and shows the tab exactly like when I perform a tab switch.
I hope that the description is clear and I hope that someone can help me.
Thanks in advice.
Regards,
Raffaele Camanzo
View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4023709#4023709
Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=4023709
18Â years, 8Â months
[JBoss jBPM] - Re: Choosing JBPM?
by kukeltje
Ed... Uhmm yes and no, Never used the word 'not' in the forum search. I often use google. could be that the keyword not is not working. That would be a shame. Still... people should at least try to search this fine forum, and if nothing comes up, post a question and MENTION they did not find anything.
Oh, and btw, yes, things are a bit looser in the Netherlands. Funny, everywhere I come in the Caribbean, especially Jamaica, they do not understand that I do not smoke pot (heck I don't even smoke at all) and never go go a prostitute (even though I'm not married and no girlfriend at the moment)
Regarding the search functionality, I'll urge the jboss people to hurry with the new forums since we have problems using them in the way they are. Thanks for telling me this.
View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4023703#4023703
Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=4023703
18Â years, 8Â months
[JBoss jBPM] - Re: Help getting all tasks for a user
by estaub
Brad,
I disagree about findPooledTaskInstances, but that may be because we're coming from different assumptions about intended use. I'm new at this, so I could easily be confused.
I assume that a task with a null actorId has not been picked up by a particular actor, but may be picked up by anyone in the pool. A task instance with the actor Id set has been "locked" for completion by a particular user, and thus is no longer assigned to the pool as a whole.
So to my thinking, the implementation is correct, and as expected; once a task has been locked to a particular user, it's no longer in the pool. For the common use-case of creating a list of pooled tasks that actors may grab a task from, this is certainly the desired behavior.
I agree that the docs could be improved!
-Ed Staub
(P.S. Did we work together in Nashua?)
View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4023701#4023701
Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=4023701
18Â years, 8Â months