[
http://jira.jboss.com/jira/browse/JBESB-1409?page=all ]
Tom Cunningham resolved JBESB-1409.
-----------------------------------
Resolution: Done
Having both the ESB/JMS message is a QS standard within the ESB project. The sendjms
option works, so there's really no reason to remove it.
Corrected the inconistencies in readme.txt. It's less complex just to leave
everything in the default location but to tell users that we are doing that rather than to
add location properties.
webservice_consumer2 QS bugs
----------------------------
Key: JBESB-1409
URL:
http://jira.jboss.com/jira/browse/JBESB-1409
Project: JBoss ESB
Issue Type: Bug
Security Level: Public(Everyone can see)
Components: Examples
Affects Versions: 4.2.1
Reporter: Jaroslaw Kijanowski
Assigned To: Tom Cunningham
Fix For: 4.2.1 CP1
1. 'sendjms' ant task shouldn't be in build.xml
2. readme.txt:
org.jboss.soa.esb.actions.soap.SOAPClient
This class is used to make the call to the webservice. It will take the
parameters that MyRequestAction set in "paramsLocation", call the
webservice, then place
the response in "responseLocation". This is zero Java code ESB wiring
in jboss-esb.xml.
This is not the case in this QS. The SOAPClient takes the WS params from the default
lcoation, and puts the response also there. 2 properties would need to be added to the
SOAPClient to have this behavior:
<property name="get-payload-location" value="paramsLocation"
/>
<property name="set-payload-location" value="responseLocation"
/>
Also both action classes, MyRequestAction and MyResponseAction, would need to be changed
to get/set the WS params from/to these locations.
--
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