Would try to set that appropriately in axis2.xml
false
false
Maybe it helps
Josef
Von: Dan Haywood [mailto:dhayw...@equalexperts.com]
Gesendet: Dienstag, 25. Oktober 2011 13:49
An: java-user@axis.apache.org
Betreff: Re: error handling
wireshark?
On 25 October 2011 10:58, Grant Maxwell wrote:
> Hi
>
> Can anyone help with this please ?
> suggestion to use tools like tcp monitor will not work. We need to get =
> the error information inside the application and handle the error.=20
>
> advice on how to get the original incoming
Hi
Can anyone help with this please ?
suggestion to use tools like tcp monitor will not work. We need to get =
the error information inside the application and handle the error.=20
advice on how to get the original incoming packet containing the error =
information would be much appreciated
rega
TCP Monitor lets you to send the message through it (change the URL
address of the request) and you can see the outgoing and incoming message.
In addition please check the stax-impl you are using
"com.ctc.wstx.exc.WstxUnexpectedCharException"
Deepal
On 10/20/2011 4:09 PM, Grant Maxwell wrote:
>
Thanks for the reply Deepal
To be clear - I need to deal with these messages in the =
application, not as an external monitor. Otherwise I will never be able =
to rely on the system for processing integrity.=09
Catching the exception is just the start. I have to be able to =
work o
Use TCP monitor [1] and log the outgoing and incoming message.
[1]: http://ws.apache.org/commons/tcpmon/download.cgi
Deepal
> Hi
>
> I am writing a java/axis2 program to access a remote service written in .Net.
>
> The problem I am having is that when the remote service does not like our
> requ
Hi
I am writing a java/axis2 program to access a remote service written in .Net.
The problem I am having is that when the remote service does not like our
request for some reason it does not return a soap message but rather outputs an
http message like:
Server was unable to process request. --
