Bug 948732 - blog example conversation problem
Summary: blog example conversation problem
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
medium
Target Milestone: CR2
: 2.2.0
Assignee: Marek Novotny
QA Contact: Marek Schmidt
URL:
Whiteboard:
Depends On: 921660
Blocks:
TreeView+ depends on / blocked
 
Reported: 2013-04-05 09:08 UTC by Marián Labuda
Modified: 2013-05-14 14:51 UTC (History)
0 users

Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Clone Of:
Environment:
Last Closed: 2013-05-14 14:51:11 UTC
Type: Bug
Embargoed:


Attachments (Terms of Use)

Description Marián Labuda 2013-04-05 09:08:18 UTC
Description of problem:
After deploying blog example from jboss-wfk-2.2.0-seam23-demo.zip pack there is a problem with the propagation of conversation. After opening any post and the attempt to change theme I'm redirected to 404.xhtml instead of changing theme of the given post


Version-Release number of selected component and comments:
-jboss-wfk-2.2.0-seam23.demo.zip pack (tried with 2.2.0.ER2 too, same results)

-build against jboss wfk 2.2.0.CR1 (jboss-wfk-2.2.0.ER2-maven-repository.zip contains older version of seam (before few commits) and it works in that older version. Problem is in 2.2.0.CR1. URLs in ER2 contain conversationIds, in CR1 is removed (perhaps conversation is not propagated well?))


Steps to Reproduce:
1. Deploy blog example from the given package
2. Go to http://localhost:8080/seam-blog/
3. Click on any post (hyperlink "[Link]")
4. Select another theme in the upper right corner from the combobox
5. Click on button "Select Theme"
6. Enjoy the 404

Comment 1 Marek Novotny 2013-04-05 10:12:30 UTC
This is fixed by reverting the patch for bz 921660

Comment 2 Marek Schmidt 2013-04-12 12:54:55 UTC
Verified on WFK 2.2.0.CR2

Comment 3 Karel Piwko 2013-05-14 14:51:11 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.