[jbossseam-issues] [JBoss JIRA] Closed: (JBSEAM-854) Explicit conversation id is lost when using nested conversation
Pete Muir (JIRA)
jira-events at lists.jboss.org
Sat Mar 1 05:34:57 EST 2008
[ http://jira.jboss.com/jira/browse/JBSEAM-854?page=all ]
Pete Muir closed JBSEAM-854.
----------------------------
Resolution: Out of Date
Explicit conversation ids are deprecated in favour of natural conversations
> Explicit conversation id is lost when using nested conversation
> ---------------------------------------------------------------
>
> Key: JBSEAM-854
> URL: http://jira.jboss.com/jira/browse/JBSEAM-854
> Project: JBoss Seam
> Issue Type: Bug
> Components: Core
> Affects Versions: 1.1.6.GA
> Environment: Linux localhost 2.6.3-7mdk #1 Wed Mar 17 15:56:42 CET 2004 i686 unknown unknown GNU/Linux
> Reporter: Yevgen Bushuyev
>
> Each click on
> <s:link id="action" value="Act" action="#{somethingHome.beginAction}"/>
> @Begin(nested=true, id="action")
> public String beginAction() {
> }
> leads to creation of a new ConversationEntry, which means that explicit id is ignored.
--
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