| Summary: | webservice_consumer1 QS bugs | ||
|---|---|---|---|
| Product: | [JBoss] JBoss Enterprise SOA Platform 4 | Reporter: | Jaroslaw Kijanowski <kijanowski> |
| Component: | JBossESB | Assignee: | Mark Little <mark.little> |
| Status: | CLOSED NEXTRELEASE | QA Contact: | |
| Severity: | high | Docs Contact: | |
| Priority: | high | ||
| Version: | 4.2 IR8 | ||
| Target Milestone: | --- | ||
| Target Release: | 4.2 Beta 2 | ||
| Hardware: | Unspecified | ||
| OS: | Unspecified | ||
| URL: | http://jira.jboss.org/jira/browse/SOA-237 | ||
| Whiteboard: | |||
| Fixed In Version: | Doc Type: | Bug Fix | |
| Doc Text: | Story Points: | --- | |
| Clone Of: | Environment: | ||
| Last Closed: | 2008-01-23 07:17:32 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: | |
Link: Added: This issue depends JBESB-1408 This was resolved in revision 17289 of ESB CP branch. verified in RC1 |
Date of First Response: 2007-12-17 14:08:23 project_key: SOA The webservice_consumer1 QS is broken in several places: 1. jboss-esb.xml contains an unused SOAPClient's "operation" property 2. the MyResponseAction action class awaits the message under "helloworld-response", but the SOAPClient puts the response under the default location - missing SOAPClient property: <property name="set-payload-location" value="helloworld-response" /> 3. deploy and run the sendjms task: 11:43:04,824 ERROR [STDERR] [Fatal Error] :1:1: Content is not allowed in prolog. 11:43:04,825 ERROR [JmsComposer] Object in JMS message has invalid XML org.xml.sax.SAXParseException: Content is not allowed in prolog. at org.apache.xerces.parsers.DOMParser.parse(Unknown Source) at org.apache.xerces.jaxp.DocumentBuilderImpl.parse(Unknown Source) at javax.xml.parsers.DocumentBuilder.parse(DocumentBuilder.java:98) at org.jboss.soa.esb.util.Util.deserialize(Util.java:223) at org.jboss.internal.soa.esb.couriers.helpers.JmsComposer.compose(JmsComposer.java:74) at org.jboss.internal.soa.esb.couriers.JmsCourier.pickup(JmsCourier.java:393) at org.jboss.internal.soa.esb.couriers.TwoWayCourierImpl.pickup(TwoWayCourierImpl.java:223) at org.jboss.internal.soa.esb.couriers.TwoWayCourierImpl.pickup(TwoWayCourierImpl.java:205) at org.jboss.soa.esb.listeners.message.MessageAwareListener.waitForEventAndProcess(MessageAwareListener.java:269) at org.jboss.soa.esb.listeners.message.MessageAwareListener.doRun(MessageAwareListener.java:253) at org.jboss.soa.esb.listeners.lifecycle.AbstractThreadedManagedLifecycle.run(AbstractThreadedManagedLifecycle.java:115) at java.lang.Thread.run(Thread.java:595) Adding a gateway to the listeners would be one possible solution...