[ http://issues.apache.org/jira/browse/AXIS-2388?page=comments#action_12365639 ]
Tom Jordahl commented on AXIS-2388: ----------------------------------- Two comments - Have you tried the latest release of Axis (1.3) or the latest SVN source from the tree? - You probably will need to debug the problem yourself as other have used WSS4J successfully to enable WS-Security with Axis. > Invalid SOAP envelope sent when ws-security is enabled > ------------------------------------------------------ > > Key: AXIS-2388 > URL: http://issues.apache.org/jira/browse/AXIS-2388 > Project: Apache Axis > Type: Bug > Versions: 1.2.1 > Environment: windows xp. > Reporter: Maximus Bond > Priority: Blocker > Attachments: SOAP Request from Axis.rtf > > I'm using Axis 1.2.1 to create proxies for a wsdl, compile them , and invoke > them to send across a SOAP request. It all worked fine. Then I enabled > ws-security by implementing a password callback handler and using a > axis.ClientConfigFile system property. Then the soap envelope going out > becomes invalid. It writes a stray </#document> tag after the > </soapenv:Envelope> tag. -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://issues.apache.org/jira/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira
