Bug 1054809
Summary: | JMS errror in mulitApp demo client | ||
---|---|---|---|
Product: | [JBoss] JBoss Fuse Service Works 6 | Reporter: | Jiri Pechanec <jpechane> |
Component: | Examples | Assignee: | Keith Babo <kbabo> |
Status: | CLOSED CURRENTRELEASE | QA Contact: | Jiri Sedlacek <jsedlace> |
Severity: | medium | Docs Contact: | |
Priority: | unspecified | ||
Version: | 6.0.0 GA | CC: | atangrin, dlesage, kconner, oskutka, soa-p-jira |
Target Milestone: | CR2 | ||
Target Release: | 6.0.0 | ||
Hardware: | Unspecified | ||
OS: | Unspecified | ||
Whiteboard: | |||
Fixed In Version: | Doc Type: | Bug Fix | |
Doc Text: |
The Camel JmsBinding formerly expected the message body returned to be a DOMSource, causing it to convert the response into an InputStream and create a BytesMessage. The body is now a Node, causing it to choose a TextMessage. As a result, mvn exec:java throws an exception.
|
Story Points: | --- |
Clone Of: | Environment: | ||
Last Closed: | 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: |
Description
Jiri Pechanec
2014-01-17 14:05:14 UTC
This occurs because the Camel JmsBinding now makes a different determination about the type of JMS message to be sent. In ER8 the body returned was a DOMSource, causing it to convert the response into an InputStream and create a BytesMessage. In CR1 the body is now a Node, causing it to choose a TextMessage. This is probably due to SWITCHYARD-1920 PR has been added for the changes Verified in CR2 Keith Babo <kbabo> updated the status of jira SWITCHYARD-1933 to Closed Keith Babo <kbabo> updated the status of jira SWITCHYARD-1920 to Closed |