On Thursday 14 February 2008, Kyle.Bober wrote: > Okay so I setup the CXF logging interceptor and this is what I now > see... > It seems that the soap:body is empty!!! Why is this happening??? > Knowing me I am making a stupid mistake on my WSDL somewhere. > Although, I used one of the simple examples as my template and just > changed some of the XSD and WSDL tags to fit my situation. Notice > anything out of the ordinary? Or maybe I am not setting up a > configuration parameter somewhere. Again, I am just running the test > client class that CXF generates for me... > > -Kyle > > Next step Wireshark setup...
Wireshark will show the same thing. Don't worry about it since the logs worked well. When you say: > Again, I am just running the test > client class that CXF generates for me... Do you litterally mean "I ran wsdl2java, compiled it, than ran the client"? If so, that's probably the issue. The client is pretty much just a stub. You probably need to go in and actually create the data that would be passed in. Without doing that, it's probably sending a null object to a bare method which probably doesn't work and would create that error. If that IS the case, you COULD try running wsdl2java with the -defaultValues switch. The client that is then generated (server as well) does throw some random data in there. The random data may not match the schema exactly, but it may work if validation is off. -- J. Daniel Kulp Principal Engineer, IONA [EMAIL PROTECTED] http://www.dankulp.com/blog
