Thanks Alex, I have updated WS-Security namespace prefix/bindings to use "wsse" and "http://docs.oasis-open.org/wss/2004/01/oasis-200401-wss-wssecurity-secext-1.0.xsd" consistently (see attached) but it still does not work.
The SOAP message sent to the endpoint still missing the header... ;-[ <?xml version="1.0" encoding="UTF-8"?> <soapenv:Envelope xmlns:soapenv="http://schemas.xmlsoap.org/soap/envelope/"> <soapenv:Header> <addr:To xmlns:addr="http://www.w3.org/2005/08/addressing">http://localhost:8080/cr-ws/services/ContentRepository</addr:To> <addr:Action xmlns:addr="http://www.w3.org/2005/08/addressing"/> <addr:ReplyTo xmlns:addr="http://www.w3.org/2005/08/addressing"> <addr:Address>http://www.w3.org/2005/08/addressing/anonymous</addr:Address> </addr:ReplyTo> <addr:MessageID xmlns:addr="http://www.w3.org/2005/08/addressing">uuid:hqejbhcnphr2q9cwji6lri</addr:MessageID> </soapenv:Header> <soapenv:Body> <axis2ns4:getVersion xmlns:axis2ns4="http://xml.spss.com/repository/remote">123.0</axis2ns4:getVersion> </soapenv:Body> </soapenv:Envelope> Thanks a lot for your help, Dmitry http://www.nabble.com/file/p13651098/HelloWord_FromBPELHelper.zip HelloWord_FromBPELHelper.zip -- View this message in context: http://www.nabble.com/Process-end-point-tf3891955.html#a13651098 Sent from the Apache Ode User mailing list archive at Nabble.com.
