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. --
Andreas
When I build the Rampart project using JDK 1.5.0_18 on Windows Vista
Starting from the root pom.xml fails with the Rampart - Integration Module in
the lengthy test . . .
When I just build the Rampart - Integration Module all works fine including the
lengthy tests, all are running all w
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 Andreas,
Guess I found what you addresses below, but thanks for the tip !
It is in the README.txt of the Apache Rampart module under release documents.
. . .
Test cases written for SAML 2.0 support requires endorsing the JDK's default
JAXP
implementation with Xerces(http://xerce
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
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:
>
