Hi Alan, to have a more concrete discussion could you post the WSDL on the list so we can see how it looks like? A sample message would surely also help.
Christian -----Ursprüngliche Nachricht----- Von: Alan Egerton [mailto:egg...@gmail.com] Gesendet: Freitag, 28. Januar 2011 12:21 An: users@cxf.apache.org Betreff: Custom WSDL binding Dear CXF Users, I am at the outset of my web service journey, but am not without some solid Java experience in other areas. After some research, I selected CXF as the framework upon which to base further exploration primarily due to its good Spring integration-but also because I can envisage going down the ESB path in the future and ServiceMix integration appears stable and mature. One of my first WS-* projects is to generate a (Java) client for a WSDL contract where the binding is not one of CXF's supported four. I had half-expected that custom bindings might (however unwelcome) be fairly commonplace given the existence of historical projects based on proprietary protocols, but a day spent with Google has yielded surprisingly little fruit. Indeed, the only ready-made solution that I can find is WSIF <http://ws.apache.org/wsif/>, but this project has been inactive for many years and is currently being moved to the Apache Attic. It appears that I have three choices and I would greatly appreciate any insight you might be able to share towards my evaluation of the relative merits/demerits of each approach. (i) add support for my required binding to CXF (or, better yet, enable CXF to load providers of custom bindings at runtime); (ii) generate the client implementation manually; or (iii) use an alternative framework (e.g. WSIF, albeit not maintained). Incidentally, in playing around with wsdl2java I edited the contract to use the pure XML binding instead (i.e. from the http://cxf.apache.org/bindings/xformat namespace) but it continues to fail with the error "WSIBP Validator found <binding> is NOT a SOAP binding". Does wsdl2java not support CXF's other bindings? Cheers, -- Alan
