I am starting to think that this is an interoperability issue with a M$ "ASMX" style Web service.
Do I need to look into using WCF to talk to it? Wes -----Original Message----- From: Gamble, Wesley (WG10) [mailto:[EMAIL PROTECTED] Sent: Monday, September 10, 2007 6:45 PM To: [email protected] Subject: RE: Can't get at SOAP error from Web Service (SOAP 1.2) -"HandlerFault is not a standard Code value" Glen, I went ahead and downloaded and configured the WSMonitor tool and have it successfully listening on localhost:4040 for WS requests to proxy. However, I cannot get the requests to go through it. Here's the relevant part of my local WSDL file: <wsdl:service name="InventoryService"> <wsdl:port name="InventoryServiceSoap" binding="tns:InventoryServiceSoap"> <soap:address location="http://localhost:4040/ChannelAdvisorAPI/v1/InventoryService.as mx" /> </wsdl:port> <wsdl:port name="InventoryServiceSoap12" binding="tns:InventoryServiceSoap12"> <!-- soap12:address location="https://api.channeladvisor.com/ChannelAdvisorAPI/v1/InventoryS ervice.asmx" / --> <soap12:address location="http://localhost:4040/ChannelAdvisorAPI/v1/InventoryService.as mx" /> </wsdl:port> </wsdl:service> I was able to put http://localhost:4040/ChannelAdvisorAPI/v1/InventoryService.asmx into a browser and have WSMonitor successfully proxy the call, as you would expect. However, it appears that my Java client (which is using this local WSDL) is not proxying the request through the WSMonitor. In my log file, I see (notice the refs. to localhost:4040): FINE: set requestContext to message be{RequestMethod=public abstract com.channeladvisor.api.webservices.APIResultOfString com.channeladvisor.api.webservices.InventoryServiceSoap.ping(), javax.xml.ws.service.endpoint.address=http://localhost:4040/ChannelAdvis orAPI/v1/InventoryService.asmx, java.lang.reflect.Method=public abstract com.channeladvisor.api.webservices.APIResultOfString com.channeladvisor.api.webservices.InventoryServiceSoap.ping(), org.apache.cxf.jaxws.context.WrappedMessageContext.SCOPES={javax.xml.ws. service.endpoint.address=APPLICATION}, org.apache.cxf.message.Message.ENDPOINT_ADDRESS=http://localhost:4040/Ch annelAdvisorAPI/v1/InventoryService.asmx} Any idea what am I doing wrong? Thanks, Wes -----Original Message----- From: Glen Mazza [mailto:[EMAIL PROTECTED] Sent: Monday, September 10, 2007 5:49 PM To: [email protected] Subject: Re: Can't get at SOAP error from Web Service (SOAP 1.2) -"HandlerFault is not a standard Code value" Am Montag, den 10.09.2007, 15:47 -0500 schrieb Gamble, Wesley (WG10): > All, > > I'm a SOAP and CXF newbie. > > SOAP 1.2 > CXF 2.0.1 > JDK 1.6.0_01 > > I'm attempting to communicate with a SOAP 1.2 Web service via CXF v. > 2.0.1. To verify that I can actually connect to the service properly, > I'm invoking a "ping" method that I am seeing. The relevant output from > my run is below. My guess is that the error message being returned from > the service can't be parsed correctly (see the message "HandlerFault is > not a standard Code value"). > > I'd like to be able to verify the contents of the outgoing and incoming > XML - how can I set things up to see the XML requests and responses (I'm > guessing some kind of logging via the CXF config. File?). > On debugging page: http://cwiki.apache.org/CXF20DOC/debugging.html Look under "WS Monitor" tool at the bottom. HTH, Glen > Thanks, > Wes >
