Bug 905033 - Seam2.3 s:link conversation propagation none broken
Summary: Seam2.3 s:link conversation propagation none broken
Keywords:
Status: CLOSED CURRENTRELEASE
Alias: None
Product: JBoss Enterprise WFK Platform 2
Classification: Retired
Component: Seam
Version: 2.2.0
Hardware: Unspecified
OS: Unspecified
unspecified
high
Target Milestone: ER2
: 2.2.0
Assignee: Marek Novotny
QA Contact: Marek Schmidt
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2013-01-28 12:23 UTC by Tomas Remes
Modified: 2013-05-14 14:54 UTC (History)
2 users (show)

Fixed In Version:
Clone Of:
Environment:
Last Closed: 2013-05-14 14:54:08 UTC
Type: Bug
Embargoed:

Attachments (Terms of Use)


Links
System ID Private Priority Status Summary Last Updated
Red Hat Issue Tracker JBSEAM-5064 0 None None None Never

Description Tomas Remes 2013-01-28 12:23:06 UTC 
Clone of JBSEAM-5064
Comment 1 Tomas Remes 2013-01-28 12:45:00 UTC 
s:link / s:button with propagation="none" does propagate conversations even when it shouldn't since the fix for JBSEAM-4976, as the conversation id gets appended always by the SeamViewHandler.

Also note that with propagation="join", the conversation id is appended two times there (once from the s:link and once by the SeamViewHandler)
Comment 4 Marek Schmidt 2013-03-15 07:47:48 UTC 
Verified on WFK 2.2.0.ER2, 

filed another BZs for other issues with s:link and conversation ids:

https://bugzilla.redhat.com/show_bug.cgi?id=920109  Seam2.3 s:link with propagation=none generates ugly URLs

https://bugzilla.redhat.com/show_bug.cgi?id=920625  Seam2.3 s:link propagation="join" conversation id is appended two times

https://bugzilla.redhat.com/show_bug.cgi?id=921660 Seam2.3 SeamViewHandler adds conversation id even if conversation is not long running
Comment 5 Karel Piwko 2013-05-14 14:54:08 UTC 
Closed as CURRENTRELEASE, part of WFK 2.2.0 distributables.
Note You need to log in before you can comment on or make changes to this bug.