Hide Forgot
Created attachment 572746 [details] Server log Seam version: 2.2.5.EAP5 (included in EAP 5.1.2.GA) The tasks example from Seam 2.2 was migrated to EAP6 according to the migration guide on Documentation-Stage (http://documentation-stage.bne.redhat.com/docs/en-US/JBoss_Enterprise_Application_Platform/6/html/Beta_Documentation/Migrate_Seam_22_Archives_to_JBoss_Enterprise_Application_Platform_6.html) and the bug was verified to occur with EAP 6.0.0.ER1. There is a patch available: https://gist.github.com/1949191 The ftest fails in 3 methods: [testng] FAILED: undoTurtleTask [testng] java.lang.AssertionError: There should NOT be a 'Undo this task' button for: Buy a turtle. expected:<false> but was:<true> [testng] at org.jboss.seam.example.tasks.test.selenium.SeleniumTasksTest.buttonMissing(SeleniumTasksTest.java:253) [testng] at org.jboss.seam.example.tasks.test.selenium.SeleniumTasksTest.undoTurtleTask(SeleniumTasksTest.java:116) [testng] ... Removed 25 stack frames [testng] FAILED: resolveTuringTask [testng] java.lang.AssertionError: There should NOT be a 'Resolve this task' button for: Build the Turing machine. expected:<false> but was:<true> [testng] at org.jboss.seam.example.tasks.test.selenium.SeleniumTasksTest.buttonMissing(SeleniumTasksTest.java:253) [testng] at org.jboss.seam.example.tasks.test.selenium.SeleniumTasksTest.resolveTuringTask(SeleniumTasksTest.java:91) [testng] ... Removed 25 stack frames [testng] FAILED: createSeleniumTask [testng] java.lang.AssertionError: There should be a 'Resolve this task' button for: Create selenium ftests for all available examples. expected:<true> but was:<false> [testng] at org.jboss.seam.example.tasks.test.selenium.SeleniumTasksTest.buttonPresent(SeleniumTasksTest.java:240) [testng] at org.jboss.seam.example.tasks.test.selenium.SeleniumTasksTest.createSeleniumTask(SeleniumTasksTest.java:149) [testng] ... Removed 25 stack frames Relevant part of server log attached.
Technical note added. If any revisions are required, please edit the "Technical Notes" field accordingly. All revisions will be proofread by the Engineering Content Services team. New Contents: The cause of this bug is the incompatibility between seam-resteasy-2.2.5.EAP5 (included in EAP 5.1.2) and RESTEasy 2.3.1.GA (included in EAP 6). This issue can be worked around by using jboss-deployment-structure.xml to exclude - resteasy-jaxrs, - resteasy-jettison-provider, - resteasy-jaxb-provider from the main deployment and - resteasy-jaxrs, - resteasy-jettison-provider, - resteasy-jaxb-provider, - resteasy-yaml-provider from the jboss-seam-tasks.war, as described in https://issues.jboss.org/browse/JBPAPP-8315. It is then necessary to include the RESTEasy libraries (bundled with Seam 2.2) in the EAR.
Technical note updated. If any revisions are required, please edit the "Technical Notes" field accordingly. All revisions will be proofread by the Engineering Content Services team. Diffed Contents: @@ -1,13 +1,12 @@ -The cause of this bug is the incompatibility between seam-resteasy-2.2.5.EAP5 (included in EAP 5.1.2) and RESTEasy 2.3.1.GA (included in EAP 6). +Due to the incompatibility between seam-resteasy-2.2.5.EAP5 and RESTEasy 2.3.1.GA, an unable to unmarshall request body error is thrown in the tasks example ftest. <procedure 1> is a workaround for this issue: -This issue can be worked around by using jboss-deployment-structure.xml to exclude +1. Exclude the following from the main deployment: - resteasy-jaxrs, - resteasy-jettison-provider, - resteasy-jaxb-provider -from the main deployment and +2. Exclude the following from the jboss-seam-tasks.war: - resteasy-jaxrs, - resteasy-jettison-provider, - resteasy-jaxb-provider, - resteasy-yaml-provider -from the jboss-seam-tasks.war, as described in https://issues.jboss.org/browse/JBPAPP-8315. +3. Include the RESTEasy libraries in the EAR (these are bundled with Seam 2.2).-It is then necessary to include the RESTEasy libraries (bundled with Seam 2.2) in the EAR.
WFK 2.0 does not delivere Seam 2.2, however, these issues have already been documented in the EAP 6 release notes, so no need to duplicate each issue in WFk 2.0 release notes. However, we should include a pointer to the EAP 6 release notes to assist customers looking for Seam 2.2 bug information.
Marek Novotny <mnovotny> updated the status of jira JBPAPP-8315 to Resolved
Russell Dickenson <rdickens> made a comment on jira JBPAPP-8315 I have reviewed this JIRA issue and the associated BZ ticket. From my perspective, this issue doesn't require a release notes entry, nor any documentation changes. Please advise me if I'm incorrect.
Marek Schmidt <maschmid> updated the status of jira JBPAPP-8315 to Closed
Marek Schmidt <maschmid> made a comment on jira JBPAPP-8315 Verified. The issue is listed in the EAP 6 Migration guide and the workaround works.