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]
