Hello,
I'm trying to use Sandesha with Rampart and I think I've found a bug.
When the server is replying to a CreateSequence message, it gets to
RampartSender,
which calls org.apache.rampart.MessageBuilder.build(MessageContext msgCtx),
which verifies that the security header is empty and tries to
Andrei,
What is the Axiom version you are using? If it is not 1.2.8 or a
recent snapshot, please check against version 1.2.8. If you can
confirm that the issue still exists in that version, please open a
JIRA issue in the WSCOMMONS project.
Regards,
Andreas
On Wed, Feb 4, 2009 at 16:08, Andrei
On Wed, Feb 4, 2009 at 5:41 PM, Andreas Veithen
andreas.veit...@gmail.com wrote:
Andrei,
What is the Axiom version you are using? If it is not 1.2.8 or a
recent snapshot, please check against version 1.2.8. If you can
confirm that the issue still exists in that version, please open a
JIRA
I guess this is a bug. No question about it.
But . Axiom is an XML object model designed to be high performant. We
can do hundreds of checks like this to make sure its integrity, conformance,
etc., IMHO, there is a part from the users side also to make things work, if
he needs performance.
Hello,
There seems to be a minor bug - or perhaps feature - in AXIOM :
One may set the attribute of an OMElement to "null" without having any
error.
But this OMElement can't be returned (as an operation response) nor be
converted to String (e.g for display purpose) : a
Hi Carlos,
Thanks for digging in to the problem. Can you please create a patch and
attach it to a JIRA (http://issues.apache.org/jira/browse/AXIS2)?
-- Chinthaka
Carlos Perez wrote:
Hi,
I have been trying to consume an Axis2 web service that returns binary
data in base64 from a .NET
Hi,
I have been trying to consume an Axis2 web service that
returns binary data in base64 from a .NET client, and the
client is complaining about invalid characters in the
base64 string. I took a look at the string and actually
the base64 string is including '=' chars in the middle of
the
