Hi Saliya, My comments:
Saliya Ekanayake-2 wrote: > > Hi Stefan, > > Yes, I am working on this issue. In fact I had some issues in developing > a back end service with message level security policies to recreate your > scenario. Probably it'll take couple of days to test and come up with a > resolution. Does it align with your schedule? > > Additionally, catching up with your email thread, I have several things > to clarify from your side. > > 1. The back end service expects a SOAP message with WS Security > information (i.e. WS Security headers are present). The response doesn't > contain any WS Security information at all. Is this the exact thing that > you are testing against? > correct Saliya Ekanayake-2 wrote: > > 2. Is there any way that I can use the same back end service to test the > scenario? If so I will require the policy that you are using as well. > Unfortunately, you can not use the same back end service because it is filtered on IP address and I have no control on this filtering. I have no problem in helping you with debugging, so if you have a build that I should use do not hesitate to contact me. Regards, Stefan. -- View this message in context: http://www.nabble.com/WSSecurityException%3A-Error-in-converting-SOAP-Envelope-to-Document-tp18058906p19250285.html Sent from the WSO2 ESB Users mailing list archive at Nabble.com. _______________________________________________ Esb-java-user mailing list [email protected] http://mailman.wso2.org/cgi-bin/mailman/listinfo/esb-java-user
