Dan, I am starting a new thread with reference to the old one http://www.nabble.com/xmlbean-binding-can-not-handle-throws-exception-tt19735873.html http://www.nabble.com/xmlbean-binding-can-not-handle-throws-exception-tt19735873.html as this is something different from the old one
I was able to resolve the issue, the issue was that Mule was expecting the WSDL Endpoint name to be as ProxyServicePort , since I had given another name to it it threw a Warning, but then it worked as part of CXF 2.1.2 even with WARNING:COULD_NOT_FIND_ENDPOINT but I guess CXF 2.1.6 has made this stricter ? I have a question here is CXF expecting the Proxy service endpoint to be named as ProxyServicePort or its Mule one, anyways I have raised this question in Mule forum also, I think it should be Mule issue, just wanted to check on the same -- View this message in context: http://www.nabble.com/Mule-and-CXF-Proxy-tp25233796p25233796.html Sent from the cxf-user mailing list archive at Nabble.com.
