This week's book giveaway is in the OO, Patterns, UML and Refactoring forum. We're giving away four copies of Refactoring for Software Design Smells: Managing Technical Debt and have Girish Suryanarayana, Ganesh Samarthyam & Tushar Sharma on-line! See this thread for details.
I currently have to consume a third party web service.
I tried using jax-rpc approach within a spring configuration file and then soon relised that I needed to create an interfaces
class on the client side (i.e. org.thirdparty.OrderService) that was identical to the one the third party web service used (i.e. containing the operation)
I also needed to create the objects that I passed and return from the operation(i.e. org.company.domain.Order) as defined in the wsdl.
From what I have put together I understand that applicationContext_ThirdPartyWS.xml will contain all the parameters that will allow spring to create a proxy to
the third party web service, enabling the client to make a call. The BeanMappingServicePostProcessor.java is used to define a complex type object, so that it can be serilized/deserilized.
For every third party web service that I deal with would I have to do all this each time?
If the parmeters that were passing and receiving were String then the client would not need to implement a BeanMappingServicePostProcessor.java and the third party ws provider would not need to create a server-config.wsdd
If I use jax-ws will I be able to just create a applicationContext_ThirdPartyWS.xml file without any ref to servicePostProcessors and by magic the client will be able to
call any third party web services?. Can anbody calrify how I can use the spring approach to consume a third party wsdl, without generating third party stub code using wsdl2java command.