| Summary: | "Unable to unmarshall request body" thrown in tasks example ftest | ||||||
|---|---|---|---|---|---|---|---|
| Product: | [Retired] JBoss Enterprise WFK Platform 2 | Reporter: | Ron Šmeral <rsmeral> | ||||
| Component: | Seam | Assignee: | Marek Novotny <mnovotny> | ||||
| Status: | CLOSED CANTFIX | QA Contact: | Ron Šmeral <rsmeral> | ||||
| Severity: | high | Docs Contact: | |||||
| Priority: | medium | ||||||
| Version: | unspecified | CC: | amelicha, kpiwko, maschmid, rnewton | ||||
| Target Milestone: | --- | ||||||
| Target Release: | 2.0.0.GA | ||||||
| Hardware: | Unspecified | ||||||
| OS: | Unspecified | ||||||
| Whiteboard: | Seam2.2 | ||||||
| Fixed In Version: | Doc Type: | Bug Fix | |||||
| Doc Text: |
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:
1. Exclude the following from the main deployment:
- resteasy-jaxrs,
- resteasy-jettison-provider,
- resteasy-jaxb-provider
2. Exclude the following from the jboss-seam-tasks.war:
- resteasy-jaxrs,
- resteasy-jettison-provider,
- resteasy-jaxb-provider,
- resteasy-yaml-provider
3. Include the RESTEasy libraries in the EAR (these are bundled with Seam 2.2).
|
Story Points: | --- | ||||
| Clone Of: | Environment: |
Fedora 16 64-bit, Mozilla Firefox 3.6.25, Oracle JDK 1.6.0_30, Seam 2.2.5.EAP5 (included in EAP 5.1.2.GA)
|
|||||
| Last Closed: | 2012-06-18 15:32:16 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: | |||||
| Attachments: |
|
||||||
|
Description
Ron Šmeral
2012-03-26 12:22:38 UTC
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. |