[jbossseam-issues] [JBoss JIRA] Created: (JBSEAM-2606) Natural conversation id already in use in seam-bay example
10:11 p.m.
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
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
3:38 p.m.
New subject: [jbossseam-issues] [JBoss JIRA] Commented: (JBSEAM-2606) Natural conversation id already in use in seam-bay example
[ http://jira.jboss.com/jira/browse/JBSEAM-2606?page=comments#action_12399044 ]
Jacob Orshalick commented on JBSEAM-2606:
-----------------------------------------
It appears the issue is that there is still a TODO to handle conversationName in
org.jboss.seam.core.ConversationPropagation.restoreNaturalConversationId(Map) which seems
to be the issue. I am adding a patch that handles retrieving the conversationId based on
the parameter sent by the s:conversationName component. This works for my implemented
example.
The disadvantage to this is that the value for the <item-id> in the seam-bay example
must be sent as an f:param. This would not be an issue if the s:conversationName tag not
only sent the provided conversationName but based on the conversationName provided
retrieved the conversation parameter-name and parameter-value from the context. This
could then be sent along with the request in the same manner as the conversationName is
currently allowing the conversation to be resumed.
What do you guys think?
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
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
3:49 p.m.
New subject: [jbossseam-issues] [JBoss JIRA] Updated: (JBSEAM-2606) Natural conversation id already in use in seam-bay example
[ http://jira.jboss.com/jira/browse/JBSEAM-2606?page=all ]
Jacob Orshalick updated JBSEAM-2606:
------------------------------------
Attachment: JBSEAM-2606-v1.patch
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
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
6:26 p.m.
New subject: [jbossseam-issues] [JBoss JIRA] Updated: (JBSEAM-2606) Natural conversation id already in use in seam-bay example
[ http://jira.jboss.com/jira/browse/JBSEAM-2606?page=all ]
Pete Muir updated JBSEAM-2606:
------------------------------
Fix Version/s: 2.1.0.GA
Assignee: Pete Muir
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
1 p.m.
New subject: [jbossseam-issues] [JBoss JIRA] Updated: (JBSEAM-2606) Natural conversation id already in use in seam-bay example
[ http://jira.jboss.com/jira/browse/JBSEAM-2606?page=all ]
Norman Richards updated JBSEAM-2606:
------------------------------------
Fix Version/s: 2.1.0.GA
(was: 2.1.0.A1)
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
1:27 a.m.
New subject: [jbossseam-issues] [JBoss JIRA] Commented: (JBSEAM-2606) Natural conversation id already in use in seam-bay example
[ 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
6:29 p.m.
New subject: [jbossseam-issues] [JBoss JIRA] Updated: (JBSEAM-2606) Natural conversation id already in use in seam-bay example
[ http://jira.jboss.com/jira/browse/JBSEAM-2606?page=all ]
Pete Muir updated JBSEAM-2606:
------------------------------
Fix Version/s: 2.1.0.GA
(was: 2.1.0.BETA1)
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
5:33 a.m.
New subject: [jbossseam-issues] [JBoss JIRA] Updated: (JBSEAM-2606) Natural conversation id already in use in seam-bay example
[ http://jira.jboss.com/jira/browse/JBSEAM-2606?page=all ]
Pete Muir updated JBSEAM-2606:
------------------------------
Fix Version/s: 2.0.2.CR1
2.1.0.BETA1
(was: 2.1.0.GA)
Assignee: Shane Bryzak (was: Pete Muir)
Yup, you are correct as always ;-)
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: Shane Bryzak
Fix For: 2.0.2.CR1, 2.1.0.BETA1
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
6:13 p.m.
New subject: [jbossseam-issues] [JBoss JIRA] Closed: (JBSEAM-2606) Natural conversation id already in use in seam-bay example
[ http://jira.jboss.com/jira/browse/JBSEAM-2606?page=all ]
Pete Muir closed JBSEAM-2606.
-----------------------------
Resolution: Done
Patch applied and backported to 2.0 branch.
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: Shane Bryzak
Fix For: 2.0.2.CR1, 2.1.0.BETA1
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
6115
days inactive
6167
days old
8 comments
4 participants
participants (4)
-
Eirik Rosvold Larsen (JIRA) -
Jacob Orshalick (JIRA)
-
Norman Richards (JIRA)
-
Pete Muir (JIRA)