axis2 - w3toppers.com

Error in WCF client consuming Axis 2 web service with WS-Security UsernameToken PasswordDigest authentication scheme

I can confirm that the UPDATE from my question actually works: object IClientMessageInspector.BeforeSendRequest(ref System.ServiceModel.Channels.Message request, System.ServiceModel.IClientChannel channel) { UsernameToken ut = new UsernameToken(“USERNAME”, “PASSWORD”, PasswordOption.SendHashed); XmlElement securityElement = ut.GetXml(new XmlDocument()); MessageHeader myHeader = MessageHeader.CreateHeader(“Security”, “http://docs.oasis-open.org/wss/2004/01/oasis-200401-wss-wssecurity-secext-1.0.xsd”, securityElement, false); request.Headers.Add(myHeader); return Convert.DBNull; } And the client: CustomBehavior behavior = new CustomBehavior(“USERNAME”, “PASSWORD”); client.Endpoint.Behaviors.Add(behavior); The error message was … Read more

Difference between Apache CXF and Axis

Keep in mind, I’m completely biased (PMC Chair of CXF), but my thoughts: From a strictly “can the project do what I need it to do” perspective, both are pretty equivalent. There some “edge case” things that CXF can do that Axis 2 cannot and vice versa. But for 90% of the use cases, either … Read more

Java Webservice Client (Best way)

What is the best approach to do this JAVA? I would personally NOT use Axis 2, even for client side development only. Here is why I stay away from it: I don’t like its architecture and hate its counter productive deployment model. I find it to be low quality project. I don’t like its performances … Read more

Content is not allowed in Prolog SAXParserException

This error is probably related to a byte order mark (BOM) prior to the actual XML content. You need to parse the returned String and discard the BOM, so SAXParser can process the document correctly. You will find a possible solution here.