[jbossseam-issues] [JBoss JIRA] Commented: (JBSEAM-2606) Natural conversation id already in use in seam-bay example

Eirik Rosvold Larsen (JIRA) jira-events at lists.jboss.org
Wed Mar 5 02:27:57 EST 2008

    [ http://jira.jboss.com/jira/browse/JBSEAM-2606?page=comments#action_12401356 ] 
Eirik Rosvold Larsen commented on JBSEAM-2606:

I think it's an excellent idea. As of now, <s:link> tags renders with "conversationId=[next conversation id]" even when you specify that you're using a natural conversation. It should render with the natural conversation parameter-name and -value instead.

Thanks for the patch Jacob, hope it makes it to 2.1.0.GA as scheduled.

> Natural conversation id already in use in seam-bay example
> ----------------------------------------------------------
>                 Key: JBSEAM-2606
>                 URL: http://jira.jboss.com/jira/browse/JBSEAM-2606
>             Project: JBoss Seam
>          Issue Type: Bug
>          Components: Core
>    Affects Versions: 2.0.1.GA
>            Reporter: Jacob Orshalick
>         Assigned To: Pete Muir
>             Fix For: 2.1.0.GA
>         Attachments: JBSEAM-2606-v1.patch
> In the seam-bay example if you view the itemdetail page, then select "Place Bid" a natural conversation is started.  Using the back button to return to itemdetail and once again selecting "Place Bid" results in:  java.lang.IllegalStateException: Conversation id is already in use: PlaceBid:<item-id>
> This has been noted in the latest from the trunk.  This may be the same issue as JBSEAM-2124.  I have also written an application that demonstrates the same issue.

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