[
http://jira.jboss.com/jira/browse/JBESB-1408?page=all ]
Mark Little updated JBESB-1408:
-------------------------------
Fix Version/s: 4.2.1 CP1
webservice_consumer1 QS bugs
----------------------------
Key: JBESB-1408
URL:
http://jira.jboss.com/jira/browse/JBESB-1408
Project: JBoss ESB
Issue Type: Bug
Security Level: Public(Everyone can see)
Components: Examples
Affects Versions: 4.2.1
Reporter: Jaroslaw Kijanowski
Fix For: 4.2.1 CP1
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 the QS 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...
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators:
http://jira.jboss.com/jira/secure/Administrators.jspa
-
For more information on JIRA, see:
http://www.atlassian.com/software/jira