I am attempting a web service integration with a third party. They have provided a jar that was built using CXF, which I am having some trouble using. It seems that the classes in the jar are looking for the wsdl on a hard-coded absolute path which does not exist on my computer. Does CXF typically hard-code this location as part of the wsdl2java step? Unfortunately I don't have access to their source, so it's making debugging difficult. I've been looking for some way to configure this wsdl path, and as I understand it, this may be possible through editing cxf.xml. The documentation regarding cxf.xml is confusing to me. I've been trying to adapt examples from pages such as http://cwiki.apache.org/CXF20DOC/jax-ws-configuration.html with little luck so far. Is there any place to find a better explanation of the jax-ws configuration that is possible in cxf.xml ? When I try to run, I get some NullPointerExceptions related to parsing my cxf.xml, but I can't tell what the exact problem is in my xml that is causing this.
Another thing I don't quite understand is why the wsdl file is even still necessary after the code has been generated. I was able to temporarily workaround the previously mentioned wsdl path issue by duplicating the specific absolute wsdl path on my computer. While this is not a solution I would like to use permanently in production, it allowed me to get past that particular problem, and create a SOAP message with this library. However I needed to connect to a different webservice URL than the original that this code was built with. I attempted to edit the wsdl to point to a different location, but it did not appear to make any difference. Does editing the wsdl after running wsdl2java have any effect on the running code? Can/Must I edit cxf.xml to deal with this situation as well? Thank You, Hans Loeblich
