Environment:WebSphere 6.0, web service gateway
Number of attachments :
Recently I faced a funny problem, namely that XFire doesn't work properly with WSDL generated by WebSphere Web Service Gateway.
This piece of, umm, IBM code can 'export' existing web services for external use, adding things like JAX-RPC handlers or WS-Security.
The funny part is that while internal WSDL comes in one piece, at the front side of the gateway WSDL is split into three chunks - main, bindings and types.
Axis 1 can understand this, suprisingly, but XFire couldn't, to my greatest sorrow.
So I dug into XFire code and finally found that org.codehaus.xfire.wsdl11.parser.WSDLServiceConfigurator contains setWrapped() method, where it is obviously assumed that ports and type definitions come always in the same piece of WSDL.
I've made a quick hack, updated WSDLServiceConfigurator is attached.
While it is not the best code I ever wrote, it solves the problem for me.