Hi Kumar!
I have the samen problem, but instead German characters they are Chinese
characters. In this case, the application crashes, because the Chinese
characters cannot be traduced to UTF-8 format.
I think it is not a problem with Axis2, just with the format of XML
documents. That is my opini
How can I open a JIRA report for this issue?
--
View this message in context:
http://old.nabble.com/SOAP-Fault-Detail-element-cannot-have-two-childs--tp31574894p31636487.html
Sent from the Axis - User mailing list archive at Nabble.com.
-
Hi!
I am using Sandesha2 module and when I provoke a MessageNumberRollover
fault, it responds with the fault, but it only includes in the Detail
element a "wsrm:Identifier" child. The WS-RM spec says that it is mandatory
to send an Identifier child and a "MaxMsgNumber" child.
http://old.nabble.c
Hi!
I have a problem when I try to use log4j to make a log (axis2.log). I'm
trying to add some headers to a message using an "OutHandler" to insert an
"unknown header" to provoke an invalid behaviour in a client of the web
service.
The matter is that when I use TCPMonitor I can see that "unknown
Hello,
I'm trying to get a log from a Secure Realiable Messaging communication
using Sandesha2 1.5 (for RM) and Rampart 1.5 (for security) modules of
Axis2. The problem that I have encountered is when I want to cause an
UnknownSequence fault in the RM Destination (the service).
To get the log o