Thanks Brett! Actually your reply had worked, I had done something else that messed me up, and I didn't the change I made wasn't applied (how silly!). Once I corrected that, I found that the WSDL was being properly formatted as wrapped, rpc/literal.
For any other readers, to consume rpc/literal, wrapped SOAP messages from Flex2, you need to set the mx:operation resultFormat attribute to "e4x" and define the namespaces of both the models and the services. It is a little more convoluted to access the response data, but I have not found a better way to wire the Flex to Spring managed beans in my business tier. Adobe Livedocs: Handling results as XML with the e4x result format http://livedocs.adobe.com/flex/2/docs/wwhelp/wwhimpl/common/html/wwhelp.htm?context=LiveDocs_Parts&file=00000460.html IBM Developerworks: Web services clients with Macrobedia Flex: http://www-128.ibm.com/developerworks/webservices/library/ws-macroflex/ Thanks! Rob On 3/28/07, Brett Knights <[EMAIL PROTECTED]> wrote:
I don't know what those tools are but if the tools are sending SOAP requests that your system doesn't understand shouldn't you be tweaking the tools' configurations or checking what SOAP bindings they understand/expect? Getting two systems to talk SOAP to each other generally means you have to use bindings that both the client and the server understand. This is a pretty good discussion of the flavors of SOAP http://www-128.ibm.com/developerworks/webservices/library/ws-whichwsdl/ The SOAP definition I sent you earlier defines the binding as rpc/literal. For the echo service it expects to see a "wrapped" SOAP request like: <?xml version="1.0" encoding="utf-8"?> <SOAP-ENV:Envelope xmlns:SOAP-ENV="http://schemas.xmlsoap.org/soap/envelope/"; xmlns:ns1="http://test.xfire.codehaus.org";> <SOAP-ENV:Body> <ns1:echo> <in0>Hello</in0> </ns1:echo> </SOAP-ENV:Body> </SOAP-ENV:Envelope> HTH Rob Dare wrote: > Thanks Brett, > > That didn't seem to help, I am stills experiencing collisions. I am > using the Eclipse WTP WSDL browser to test (and also my Flex2 > application). Both are still only sending the parameter in the soap > body. > > - Rob > > > On 3/28/07, Brett Knights <[EMAIL PROTECTED]> wrote: >> I basically followed the Appfuse tutorial for XFire with good results. >> I have exposed interfaces that are usable at least by php5 SOAP clients >> by declaring my web service like: >> >> <bean name="userService" >> class="org.codehaus.xfire.spring.ServiceBean"> >> <property name="serviceBean" ref="wsSalesOrderProcessor"/> >> <property name="serviceClass" >> value="net.qicnet.qicnet.service.ws.OrderWebService"/> >> <property name="style" value="rpc"/> >> <property name="use" value="literal"/> >> <property name="inHandlers"> >> <list> >> <ref bean="addressingHandler"/> >> </list> >> </property> >> </bean> >> >> Then I access the service from PHP5 with: >> >> $client = >> WSDLProxyGenerator::createSoapClient(QN_ORDER_WSDL_LOCATION,'QN',array( >> 'trace' => 1, >> 'soap_version' => SOAP_1_1, >> 'style' => SOAP_RPC, >> 'encoding' => SOAP_LITERAL, >> 'login' => QN_QT_LOGIN, >> 'password' => QN_QT_PW >> )); >> >> >> HTH >> Brett Knights >> >> >> Rob Dare wrote: >> > Does anyone have some insight into exposing Spring managed >> > beans as XFire Web Services? >> > >> > I am experiencing collisions in the XFire engine with service methods >> > having the same parameter signatures (or no parameters). >> > >> > This issue (though not directly related to XFire) is described in >> > this article: >> > >> http://myarch.com/wrappernon-wrapper-web-service-styles-things-you-need-to-know >> >> > >> > >> > Any thoughts, hints, URLs, etc that can be shared would be greatly >> > appreciated. >> > >> > Thanks, >> > >> > Rob >> > >> > --------------------------------------------------------------------- >> > To unsubscribe, e-mail: [EMAIL PROTECTED] >> > For additional commands, e-mail: [EMAIL PROTECTED] >> > >> > >> > >> >> --------------------------------------------------------------------- >> To unsubscribe, e-mail: [EMAIL PROTECTED] >> For additional commands, e-mail: [EMAIL PROTECTED] >> >> > > --------------------------------------------------------------------- > To unsubscribe, e-mail: [EMAIL PROTECTED] > For additional commands, e-mail: [EMAIL PROTECTED] > > > --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
--------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
