Hello,
 
I currently have a web service client that is generated through Weblogic
8.1's built in WSDL2Java tool (I think Weblogic's tool is based on Axis
1.x).  I want to move away from the Weblogic implementation to a more
modern and robust implementation.
 
I decided to evaluate both Axis2 and CXF, as I've heard good things
about XFire in the past.  I used the Axis2 WSDL2Java tool to create the
web service client and successfully tested the client.  
 
I did the same using CXF, using the WSDLToJava tool to generate the
client stubs.  When I first attempted to test the client stubs it failed
due to a connection timeout, because I hadn't configured CXF to get
through our corporate proxy.
 
Once I did that, when I run the test, it fails with this error:
 
org.apache.cxf.binding.soap.SoapFault: Server did not recognize the
value of HTTP Header SOAPAction: .
 
I can't for the life of me figure out what might be wrong.  Notice that
there's no text between the colon and the period at the end of the
message.  It appears that some text should be there.
 
I'm pretty sure the WSDL and the service is valid because I currently
use the client stubs generated by Weblogic in production, and I was able
to (fairly easily) get the client stubs working with Axis2, but CXF
fails.
 
Any ideas on what might be wrong, or where I should look?
 
Thank you!!!
 
-Ryan
 
 

This e-mail message is being sent solely for use by the intended recipient(s) 
and may contain confidential information.  Any unauthorized review, use, 
disclosure or distribution is prohibited.  If you are not the intended 
recipient, please contact the sender by phone or reply by e-mail, delete the 
original message and destroy all copies. Thank you.

Reply via email to