Bug 920109

Summary: Seam2.3 s:link with propagation=none generates ugly URLs
Product: [Retired] JBoss Enterprise WFK Platform 2 Reporter: Marek Schmidt <maschmid>
Component: SeamAssignee: Marek Novotny <mnovotny>
Status: CLOSED CURRENTRELEASE QA Contact: Marek Schmidt <maschmid>
Severity: high Docs Contact:
Priority: unspecified    
Version: 2.2.0CC: myarboro
Target Milestone: CR1   
Target Release: 2.2.0   
Hardware: Unspecified   
OS: Unspecified   
Whiteboard:
Fixed In Version: Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2013-05-14 14:54:06 UTC Type: Bug
Regression: --- Mount Type: ---
Documentation: --- CRM:
Verified Versions: Category: ---
oVirt Team: --- RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: --- Target Upstream Version:
Embargoed:
Bug Depends On: 921660    
Bug Blocks:    

Description Marek Schmidt 2013-03-11 11:15:00 UTC 
Description of problem:

s:link with propagation="none" (e.g. <s:link id="link" view="/entry.xhtml" propagation="none">... ) generates URLs such as 

http://127.0.0.1:8080/seam-blog/entry?conversationId=5&conversationPropagation=none 

which are ugly as they contain unnecessary conversationId parameter. In previous Seam 2.2 version, such s:link would generate a nice URL, e.g.:

http://127.0.0.1:8080/seam-blog/entry

This is problem especially with pages.xml rewrite mechanism, where it is a common practice to use s:link with propagation=none especially for the reason that it generates nice bookmarkable URLs, so this behavior is a severe regression. See e.g. the blog example.

Version-Release number of selected component (if applicable):

WFK 2.2.0.ER2 Seam 2.3.1.Final-redhat-1
Comment 1 Marek Novotny 2013-03-25 09:10:07 UTC 
Fixed by fixing https://source.jboss.org/changelog/Seam?cs=15467
Comment 2 Marek Novotny 2013-03-25 10:02:15 UTC 
As Marek raised question the above commit was as final, I did a commit to remove adding of propagation parameter in https://source.jboss.org/changelog/Seam?cs=15458
Comment 3 Marek Schmidt 2013-04-03 07:29:26 UTC 
Verified on WFK 2.2.0.CR1

(no docs text, as this issue is was not present in any previously released version)
Comment 4 Karel Piwko 2013-05-14 14:54:06 UTC 
Closed as CURRENTRELEASE, part of WFK 2.2.0 distributables.