[
http://jira.jboss.com/jira/browse/JBESB-1102?page=all ]
Tom Fennelly closed JBESB-1102.
-------------------------------
Resolution: Done
Fixed.
The sample couldn't work with "Option #1" because it's an RPC style
interface and there was no request object wrapping the Order instance. I created a
ProcessOrderRequest, set the order on this and set the ProcessOrderRequest on the request
param map.
webservice_consumer2 quickstart Option #1 request markup does not
work
----------------------------------------------------------------------
Key: JBESB-1102
URL:
http://jira.jboss.com/jira/browse/JBESB-1102
Project: JBoss ESB
Issue Type: Bug
Security Level: Public(Everyone can see)
Components: Web Services
Affects Versions: 4.2.1 IR1
Environment: ESB head using JBossAS 4.2.1 with JBossWS 2.0.0 and the
"patch-jbossws" target.
Reporter: James Williams
Assigned To: Tom Fennelly
Priority: Minor
Fix For: 4.2.1 IR2
This wiki mentions two different options for SOAPClient requests. I have a quickstart for
both styles, called "webservice_consumer2". It appears as though "Option
1" does not work. It seems as though the request parameters are not getting mapped to
SOAP parameters correctly. To test this, just run the "webservice_consumer2"
quickstart with the jboss-esb.xml markup for the request action that looks like:
<action name="request-mapper"
class="org.jboss.soa.esb.samples.quickstart.webservice_consumer2.MyRequestAction"
process="option1">
</action>
The default markup for the quickstart is:
<action name="request-mapper"
class="org.jboss.soa.esb.samples.quickstart.webservice_consumer2.MyRequestAction"
process="option2">
</action>
I did this to keep the quickstart from blowing up, but I think "Option 1"
should probably be the default.
--
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