You are viewing a plain text version of this content. The canonical link for it is here.
Posted to users@cxf.apache.org by Glen Mazza <gl...@verizon.net> on 2007/09/11 00:49:08 UTC

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
>

RE: Can't get at SOAP error from Web Service (SOAP 1.2)-"HandlerFault is not a standard Code value"

Posted by "Gamble, Wesley (WG10)" <WG...@tmw.com>.
Glen, 


> 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):
> 

I'm not sure why you think your client is *not* proxying the
request--the very fact that it's going to localhost:4040 would indicate
that it is doing that, no?

I think my client is not proxying the request because when I did it
through the browser, I saw the request in 
Wsmonitor, but when I tried to do it with my client, I did _not_ see the
request in Wsmonitor.

WG

RE: Can't get at SOAP error from Web Service (SOAP 1.2)-"HandlerFault is not a standard Code value"

Posted by Glen Mazza <gl...@verizon.net>.
Am Dienstag, den 11.09.2007, 09:55 -0500 schrieb Gamble, Wesley (WG10):
> Glen,
> 
> Upon further investigation, I think that you are right and my message is
> not being sent.  If you look at the error trace below, it kind of looks
> like this error is being thrown from within one of the _outbound_
> interceptors before the message even goes across the wire.  Apparently,
> the SOAPOutInterceptor is failing on this call at this line
> 
>  

<snip/>

> (I'd just like to point out that if this is correct, the CXF is throwing
> a HandlerFault which a later part of the code rejects as being
> non-standard - huh?).
> 
> I may take a look at Axis2 if I can't make any progress on this.
> 

I don't know enough about the code to comment on your error, but if you
have to switch, I would look at Glassfish Metro (links below) first
before Axis--it is more in line with what CXF offers, so it is easier to
switch between the two.

Glen

https://metro.dev.java.net/
https://jax-ws.dev.java.net/guide/

> Thanks,
> Wes

RE: Can't get at SOAP error from Web Service (SOAP 1.2)-"HandlerFault is not a standard Code value"

Posted by "Gamble, Wesley (WG10)" <WG...@tmw.com>.
Glen,

Upon further investigation, I think that you are right and my message is
not being sent.  If you look at the error trace below, it kind of looks
like this error is being thrown from within one of the _outbound_
interceptors before the message even goes across the wire.  Apparently,
the SOAPOutInterceptor is failing on this call at this line

 
org.apache.cxf.binding.soap.interceptor.SoapOutInterceptor.handleHeaderP
art(SoapOutInterceptor.java:179)

which will end up causing an index out of bounds error.

I did make some mods. to a class of APICredentials which are required in
the SOAP header.   But all I did was initialize the String variables to
be the userid and password required by the services.  Here's a snippet
of that:

@XmlAccessorType(XmlAccessType.FIELD)
@XmlType(name = "APICredentials", propOrder = {"developerKey",
"password"})
public class APICredentials {

    @XmlElement(name = "DeveloperKey", namespace =
"http://api.channeladvisor.com/webservices/")
    protected String developerKey = "<key>";    
    @XmlElement(name = "Password", namespace =
"http://api.channeladvisor.com/webservices/")
    protected String password = "<pwd>";
    @XmlAnyAttribute
    private Map<QName, String> otherAttributes = new HashMap<QName,
String>();

(I'd just like to point out that if this is correct, the CXF is throwing
a HandlerFault which a later part of the code rejects as being
non-standard - huh?).

I may take a look at Axis2 if I can't make any progress on this.

Thanks,
Wes

=========================snippet of FINE log
output===============================

FINE: registering incoming observer:
org.apache.cxf.endpoint.ClientImpl@c8e4de
Invoking ping...
Sep 11, 2007 9:32:29 AM
org.apache.cxf.configuration.spring.ConfigurerImpl configureBean
FINE: Could not find a definition for bean with id
{http://api.channeladvisor.com/webservices/}InventoryService - no
injection will be performed.
Sep 11, 2007 9:32:29 AM
org.apache.cxf.configuration.spring.ConfigurerImpl configureBean
FINE: Could not find a definition for bean with id
{http://api.channeladvisor.com/webservices/}InventoryServiceSoap12.endpo
int - no injection will be performed.
Sep 11, 2007 9:32:29 AM
org.apache.cxf.jaxws.handler.AnnotationHandlerChainBuilder
buildHandlerChainFromClass
FINE: building handler chain
Sep 11, 2007 9:32:29 AM
org.apache.cxf.jaxws.handler.AnnotationHandlerChainBuilder
findHandlerChainAnnotation
FINE: Checking for HandlerChain annotation on
com.channeladvisor.api.webservices.InventoryService
Sep 11, 2007 9:32:29 AM
org.apache.cxf.jaxws.handler.AnnotationHandlerChainBuilder
buildHandlerChainFromClass
FINE: no HandlerChain annotation on class
com.channeladvisor.api.webservices.InventoryService
Sep 11, 2007 9:32:29 AM org.apache.cxf.jaxws.ServiceImpl createPort
FINE: created proxy
Sep 11, 2007 9:32:29 AM org.apache.cxf.endpoint.ClientImpl invoke
FINE: Invoke, operation info: [BindingOperationInfo:
{http://api.channeladvisor.com/webservices/}Ping], params:
[Ljava.lang.Object;@80ed90
Sep 11, 2007 9:32:29 AM org.apache.cxf.endpoint.ClientImpl setContext
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}
Sep 11, 2007 9:32:29 AM org.apache.cxf.endpoint.ClientImpl
setupInterceptorChain
FINE: Interceptors contributed by bus: []
Sep 11, 2007 9:32:29 AM org.apache.cxf.endpoint.ClientImpl
setupInterceptorChain
FINE: Interceptors contributed by endpoint:
[org.apache.cxf.interceptor.MessageSenderInterceptor@1d8417c,
org.apache.cxf.jaxws.interceptors.SwAOutInterceptor@b34646,
org.apache.cxf.jaxws.handler.logical.LogicalHandlerOutInterceptor@1cac3f
a, org.apache.cxf.jaxws.interceptors.WrapperClassOutInterceptor@10872ce,
org.apache.cxf.jaxws.interceptors.HolderOutInterceptor@1a93f38,
org.apache.cxf.jaxws.handler.soap.SOAPHandlerInterceptor@75b3ee]
Sep 11, 2007 9:32:29 AM org.apache.cxf.endpoint.ClientImpl
setupInterceptorChain
FINE: Interceptors contributed by client: []
Sep 11, 2007 9:32:29 AM org.apache.cxf.endpoint.ClientImpl
setupInterceptorChain
FINE: Interceptors contributed by binding:
[org.apache.cxf.binding.soap.interceptor.SoapActionOutInterceptor@177fa9
a, org.apache.cxf.interceptor.AttachmentOutInterceptor@1e5ba24,
org.apache.cxf.interceptor.StaxOutInterceptor@11fc4b8,
org.apache.cxf.binding.soap.interceptor.SoapHeaderOutFilterInterceptor@a
c4d3b, org.apache.cxf.interceptor.WrappedOutInterceptor@29d75,
org.apache.cxf.interceptor.BareOutInterceptor@1af9e98,
org.apache.cxf.binding.soap.interceptor.SoapPreProtocolOutInterceptor@d5
1a54, org.apache.cxf.binding.soap.interceptor.SoapOutInterceptor@b3ae5c]
Sep 11, 2007 9:32:29 AM org.apache.cxf.phase.PhaseInterceptorChain add
FINE: Adding interceptor
org.apache.cxf.interceptor.MessageSenderInterceptor@1d8417c to phase
prepare-send
Sep 11, 2007 9:32:29 AM org.apache.cxf.phase.PhaseInterceptorChain add
FINE: Adding interceptor
org.apache.cxf.jaxws.interceptors.SwAOutInterceptor@b34646 to phase
pre-logical
Sep 11, 2007 9:32:29 AM org.apache.cxf.phase.PhaseInterceptorChain add
FINE: Adding interceptor
org.apache.cxf.jaxws.handler.logical.LogicalHandlerOutInterceptor@1cac3f
a to phase pre-marshal
Sep 11, 2007 9:32:29 AM org.apache.cxf.phase.PhaseInterceptorChain add
FINE: Adding interceptor
org.apache.cxf.jaxws.interceptors.WrapperClassOutInterceptor@10872ce to
phase pre-logical
Sep 11, 2007 9:32:29 AM org.apache.cxf.phase.PhaseInterceptorChain add
FINE: Adding interceptor
org.apache.cxf.jaxws.interceptors.HolderOutInterceptor@1a93f38 to phase
pre-logical
Sep 11, 2007 9:32:29 AM org.apache.cxf.phase.PhaseInterceptorChain add
FINE: Adding interceptor
org.apache.cxf.jaxws.handler.soap.SOAPHandlerInterceptor@75b3ee to phase
pre-protocol
Sep 11, 2007 9:32:29 AM org.apache.cxf.phase.PhaseInterceptorChain add
FINE: Adding interceptor
org.apache.cxf.binding.soap.interceptor.SoapActionOutInterceptor@177fa9a
to phase post-logical
Sep 11, 2007 9:32:29 AM org.apache.cxf.phase.PhaseInterceptorChain add
FINE: Adding interceptor
org.apache.cxf.interceptor.AttachmentOutInterceptor@1e5ba24 to phase
pre-stream
Sep 11, 2007 9:32:29 AM org.apache.cxf.phase.PhaseInterceptorChain add
FINE: Adding interceptor
org.apache.cxf.interceptor.StaxOutInterceptor@11fc4b8 to phase
pre-stream
Sep 11, 2007 9:32:29 AM org.apache.cxf.phase.PhaseInterceptorChain add
FINE: Adding interceptor
org.apache.cxf.binding.soap.interceptor.SoapHeaderOutFilterInterceptor@a
c4d3b to phase pre-logical
Sep 11, 2007 9:32:29 AM org.apache.cxf.phase.PhaseInterceptorChain add
FINE: Adding interceptor
org.apache.cxf.interceptor.WrappedOutInterceptor@29d75 to phase marshal
Sep 11, 2007 9:32:29 AM org.apache.cxf.phase.PhaseInterceptorChain add
FINE: Adding interceptor
org.apache.cxf.interceptor.BareOutInterceptor@1af9e98 to phase marshal
Sep 11, 2007 9:32:29 AM org.apache.cxf.phase.PhaseInterceptorChain add
FINE: Adding interceptor
org.apache.cxf.binding.soap.interceptor.SoapPreProtocolOutInterceptor@d5
1a54 to phase pre-stream
Sep 11, 2007 9:32:29 AM org.apache.cxf.phase.PhaseInterceptorChain add
FINE: Adding interceptor
org.apache.cxf.binding.soap.interceptor.SoapOutInterceptor@b3ae5c to
phase write
Sep 11, 2007 9:32:29 AM org.apache.cxf.phase.PhaseInterceptorChain
outputChainToLog
FINE: Chain org.apache.cxf.phase.PhaseInterceptorChain@1af4309 was
created. Current flow:
  pre-logical [HolderOutInterceptor, SwAOutInterceptor,
WrapperClassOutInterceptor, SoapHeaderOutFilterInterceptor]
  post-logical [SoapActionOutInterceptor]
  prepare-send [MessageSenderInterceptor]
  pre-stream [SoapPreProtocolOutInterceptor, AttachmentOutInterceptor,
StaxOutInterceptor]
  pre-protocol [SOAPHandlerInterceptor]
  write [SoapOutInterceptor]
  pre-marshal [LogicalHandlerOutInterceptor]
  marshal [WrappedOutInterceptor, BareOutInterceptor]

Sep 11, 2007 9:32:29 AM org.apache.cxf.phase.PhaseInterceptorChain
doIntercept
FINE: Invoking handleMessage on interceptor
org.apache.cxf.jaxws.interceptors.HolderOutInterceptor@1a93f38
Sep 11, 2007 9:32:29 AM
org.apache.cxf.jaxws.interceptors.HolderOutInterceptor handleMessage
FINE: op: [OperationInfo:
{http://api.channeladvisor.com/webservices/}Ping]
Sep 11, 2007 9:32:29 AM
org.apache.cxf.jaxws.interceptors.HolderOutInterceptor handleMessage
FINE: op.hasOutput(): true
Sep 11, 2007 9:32:29 AM
org.apache.cxf.jaxws.interceptors.HolderOutInterceptor handleMessage
FINE: op.getOutput().size(): 1
Sep 11, 2007 9:32:29 AM org.apache.cxf.phase.PhaseInterceptorChain
doIntercept
FINE: Invoking handleMessage on interceptor
org.apache.cxf.jaxws.interceptors.SwAOutInterceptor@b34646
Sep 11, 2007 9:32:29 AM org.apache.cxf.phase.PhaseInterceptorChain
doIntercept
FINE: Invoking handleMessage on interceptor
org.apache.cxf.jaxws.interceptors.WrapperClassOutInterceptor@10872ce
Sep 11, 2007 9:32:29 AM org.apache.cxf.phase.PhaseInterceptorChain
doIntercept
FINE: Invoking handleMessage on interceptor
org.apache.cxf.binding.soap.interceptor.SoapHeaderOutFilterInterceptor@a
c4d3b
Sep 11, 2007 9:32:29 AM org.apache.cxf.phase.PhaseInterceptorChain
doIntercept
FINE: Invoking handleMessage on interceptor
org.apache.cxf.binding.soap.interceptor.SoapActionOutInterceptor@177fa9a
Sep 11, 2007 9:32:29 AM org.apache.cxf.phase.PhaseInterceptorChain
doIntercept
FINE: Invoking handleMessage on interceptor
org.apache.cxf.interceptor.MessageSenderInterceptor@1d8417c
Sep 11, 2007 9:32:29 AM org.apache.cxf.phase.PhaseInterceptorChain add
FINE: Adding interceptor
org.apache.cxf.interceptor.MessageSenderInterceptor$MessageSenderEndingI
nterceptor@1e3cc77 to phase prepare-send-ending
Sep 11, 2007 9:32:29 AM org.apache.cxf.phase.PhaseInterceptorChain
outputChainToLog
FINE: Chain org.apache.cxf.phase.PhaseInterceptorChain@1af4309 was
modified. Current flow:
  pre-logical [HolderOutInterceptor, SwAOutInterceptor,
WrapperClassOutInterceptor, SoapHeaderOutFilterInterceptor]
  post-logical [SoapActionOutInterceptor]
  prepare-send [MessageSenderInterceptor]
  pre-stream [SoapPreProtocolOutInterceptor, AttachmentOutInterceptor,
StaxOutInterceptor]
  pre-protocol [SOAPHandlerInterceptor]
  write [SoapOutInterceptor]
  pre-marshal [LogicalHandlerOutInterceptor]
  marshal [WrappedOutInterceptor, BareOutInterceptor]
  prepare-send-ending [MessageSenderEndingInterceptor]

Sep 11, 2007 9:32:29 AM org.apache.cxf.phase.PhaseInterceptorChain
doIntercept
FINE: Invoking handleMessage on interceptor
org.apache.cxf.binding.soap.interceptor.SoapPreProtocolOutInterceptor@d5
1a54
Sep 11, 2007 9:32:29 AM org.apache.cxf.phase.PhaseInterceptorChain
doIntercept
FINE: Invoking handleMessage on interceptor
org.apache.cxf.interceptor.AttachmentOutInterceptor@1e5ba24
Sep 11, 2007 9:32:29 AM org.apache.cxf.phase.PhaseInterceptorChain
doIntercept
FINE: Invoking handleMessage on interceptor
org.apache.cxf.interceptor.StaxOutInterceptor@11fc4b8
Sep 11, 2007 9:32:29 AM org.apache.cxf.phase.PhaseInterceptorChain add
FINE: Adding interceptor
org.apache.cxf.interceptor.StaxOutInterceptor$StaxOutEndingInterceptor@1
6721bd to phase pre-stream-ending
Sep 11, 2007 9:32:29 AM org.apache.cxf.phase.PhaseInterceptorChain
outputChainToLog
FINE: Chain org.apache.cxf.phase.PhaseInterceptorChain@1af4309 was
modified. Current flow:
  pre-logical [HolderOutInterceptor, SwAOutInterceptor,
WrapperClassOutInterceptor, SoapHeaderOutFilterInterceptor]
  post-logical [SoapActionOutInterceptor]
  prepare-send [MessageSenderInterceptor]
  pre-stream [SoapPreProtocolOutInterceptor, AttachmentOutInterceptor,
StaxOutInterceptor]
  pre-protocol [SOAPHandlerInterceptor]
  write [SoapOutInterceptor]
  pre-marshal [LogicalHandlerOutInterceptor]
  marshal [WrappedOutInterceptor, BareOutInterceptor]
  pre-stream-ending [StaxOutEndingInterceptor]
  prepare-send-ending [MessageSenderEndingInterceptor]

Sep 11, 2007 9:32:29 AM org.apache.cxf.phase.PhaseInterceptorChain
doIntercept
FINE: Invoking handleMessage on interceptor
org.apache.cxf.jaxws.handler.soap.SOAPHandlerInterceptor@75b3ee
Sep 11, 2007 9:32:29 AM org.apache.cxf.jaxws.handler.HandlerChainInvoker
<init>
FINE: invoker for chain size: 0
Sep 11, 2007 9:32:29 AM org.apache.cxf.phase.PhaseInterceptorChain
doIntercept
FINE: Invoking handleMessage on interceptor
org.apache.cxf.binding.soap.interceptor.SoapOutInterceptor@b3ae5c
Sep 11, 2007 9:32:29 AM org.apache.cxf.phase.PhaseInterceptorChain
doIntercept
INFO: Interceptor has thrown exception, unwinding now
java.lang.IndexOutOfBoundsException: Index: 1, Size: 1
	at java.util.ArrayList.RangeCheck(ArrayList.java:547)
	at java.util.ArrayList.get(ArrayList.java:322)
	at
org.apache.cxf.message.MessageContentsList.get(MessageContentsList.java:
76)
	at
org.apache.cxf.binding.soap.interceptor.SoapOutInterceptor.handleHeaderP
art(SoapOutInterceptor.java:179)
	at
org.apache.cxf.binding.soap.interceptor.SoapOutInterceptor.writeSoapEnve
lopeStart(SoapOutInterceptor.java:124)
	at
org.apache.cxf.binding.soap.interceptor.SoapOutInterceptor.handleMessage
(SoapOutInterceptor.java:76)
	at
org.apache.cxf.binding.soap.interceptor.SoapOutInterceptor.handleMessage
(SoapOutInterceptor.java:57)
	at
org.apache.cxf.phase.PhaseInterceptorChain.doIntercept(PhaseInterceptorC
hain.java:207)
	at
org.apache.cxf.endpoint.ClientImpl.invoke(ClientImpl.java:254)
	at
org.apache.cxf.endpoint.ClientImpl.invoke(ClientImpl.java:205)
	at
org.apache.cxf.frontend.ClientProxy.invokeSync(ClientProxy.java:73)
	at
org.apache.cxf.jaxws.JaxWsClientProxy.invoke(JaxWsClientProxy.java:135)
	at $Proxy32.ping(Unknown Source)
	at
com.channeladvisor.api.webservices.InventoryServiceSoap12_Client.main(In
ventoryServiceSoap12_Client.java:88)
Sep 11, 2007 9:32:29 AM org.apache.cxf.phase.PhaseInterceptorChain
unwind
FINE: Invoking handleFault on interceptor
org.apache.cxf.binding.soap.interceptor.SoapOutInterceptor@b3ae5c
Sep 11, 2007 9:32:29 AM org.apache.cxf.phase.PhaseInterceptorChain
unwind
FINE: Invoking handleFault on interceptor
org.apache.cxf.jaxws.handler.soap.SOAPHandlerInterceptor@75b3ee
Sep 11, 2007 9:32:29 AM org.apache.cxf.phase.PhaseInterceptorChain
unwind
FINE: Invoking handleFault on interceptor
org.apache.cxf.interceptor.StaxOutInterceptor@11fc4b8
Sep 11, 2007 9:32:29 AM org.apache.cxf.phase.PhaseInterceptorChain
unwind
FINE: Invoking handleFault on interceptor
org.apache.cxf.interceptor.AttachmentOutInterceptor@1e5ba24
Sep 11, 2007 9:32:29 AM org.apache.cxf.phase.PhaseInterceptorChain
unwind
FINE: Invoking handleFault on interceptor
org.apache.cxf.binding.soap.interceptor.SoapPreProtocolOutInterceptor@d5
1a54
Sep 11, 2007 9:32:29 AM org.apache.cxf.phase.PhaseInterceptorChain
unwind
FINE: Invoking handleFault on interceptor
org.apache.cxf.interceptor.MessageSenderInterceptor@1d8417c
Sep 11, 2007 9:32:29 AM org.apache.cxf.phase.PhaseInterceptorChain
unwind
FINE: Invoking handleFault on interceptor
org.apache.cxf.binding.soap.interceptor.SoapActionOutInterceptor@177fa9a
Sep 11, 2007 9:32:29 AM org.apache.cxf.phase.PhaseInterceptorChain
unwind
FINE: Invoking handleFault on interceptor
org.apache.cxf.binding.soap.interceptor.SoapHeaderOutFilterInterceptor@a
c4d3b
Sep 11, 2007 9:32:29 AM org.apache.cxf.phase.PhaseInterceptorChain
unwind
FINE: Invoking handleFault on interceptor
org.apache.cxf.jaxws.interceptors.WrapperClassOutInterceptor@10872ce
Sep 11, 2007 9:32:29 AM org.apache.cxf.phase.PhaseInterceptorChain
unwind
FINE: Invoking handleFault on interceptor
org.apache.cxf.jaxws.interceptors.SwAOutInterceptor@b34646
Sep 11, 2007 9:32:29 AM org.apache.cxf.phase.PhaseInterceptorChain
unwind
FINE: Invoking handleFault on interceptor
org.apache.cxf.jaxws.interceptors.HolderOutInterceptor@1a93f38
Sep 11, 2007 9:32:29 AM
com.sun.xml.internal.messaging.saaj.soap.ver1_2.Fault1_2Impl
checkIfStandardFaultCode
SEVERE: SAAJ0435: {http://cxf.apache.org/faultcode}HandlerFault is not a
standard Code value
Exception in thread "main"
java.lang.reflect.UndeclaredThrowableException
	at $Proxy32.ping(Unknown Source)
	at
com.channeladvisor.api.webservices.InventoryServiceSoap12_Client.main(In
ventoryServiceSoap12_Client.java:88)
Caused by: com.sun.xml.internal.messaging.saaj.SOAPExceptionImpl:
{http://cxf.apache.org/faultcode}HandlerFault is not a standard Code
value
	at
com.sun.xml.internal.messaging.saaj.soap.ver1_2.Fault1_2Impl.checkIfStan
dardFaultCode(Fault1_2Impl.java:134)
	at
com.sun.xml.internal.messaging.saaj.soap.impl.FaultImpl.setFaultCode(Fau
ltImpl.java:124)
	at
com.sun.xml.internal.messaging.saaj.soap.impl.FaultImpl.setFaultCode(Fau
ltImpl.java:138)
	at
org.apache.cxf.jaxws.JaxWsClientProxy.invoke(JaxWsClientProxy.java:162)
	... 2 more 

-----Original Message-----
From: Glen Mazza [mailto:glen.mazza@verizon.net] 
Sent: Monday, September 10, 2007 8:56 PM
To: cxf-user@incubator.apache.org
Subject: RE: Can't get at SOAP error from Web Service (SOAP
1.2)-"HandlerFault is not a standard Code value"

> 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):
> 

I'm not sure why you think your client is *not* proxying the
request--the very fact that it's going to localhost:4040 would indicate
that it is doing that, no?

Glen

> 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
>

RE: Can't get at SOAP error from Web Service (SOAP 1.2) -"HandlerFault is not a standard Code value"

Posted by Glen Mazza <gl...@verizon.net>.
Am Montag, den 10.09.2007, 18:48 -0500 schrieb Gamble, Wesley (WG10):
> 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?
> 

Sorry, I don't know Microsoft's products.

<snip/>

> 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):
> 

I'm not sure why you think your client is *not* proxying the
request--the very fact that it's going to localhost:4040 would indicate
that it is doing that, no?

Glen

> 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
>

RE: Can't get at SOAP error from Web Service (SOAP 1.2) -"HandlerFault is not a standard Code value"

Posted by "Gamble, Wesley (WG10)" <WG...@tmw.com>.
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:WG10@tmw.com] 
Sent: Monday, September 10, 2007 6:45 PM
To: cxf-user@incubator.apache.org
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:glen.mazza@verizon.net] 
Sent: Monday, September 10, 2007 5:49 PM
To: cxf-user@incubator.apache.org
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
>

RE: Can't get at SOAP error from Web Service (SOAP 1.2) -"HandlerFault is not a standard Code value"

Posted by "Gamble, Wesley (WG10)" <WG...@tmw.com>.
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:glen.mazza@verizon.net] 
Sent: Monday, September 10, 2007 5:49 PM
To: cxf-user@incubator.apache.org
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
>