Search:

Type: Posts; User: uwieske; Keyword(s):

Search: Search took 0.01 seconds.

  1. Not sure I understand your problem... Does the...

    Not sure I understand your problem...
    Does the client send headers with soap:mustUnderstand="1" for WSSE headers?
    Try sending in messages with mustUnderstand="0" for the WSSE headers.
    Are you...
  2. Spring WS is mixing up WSSE namespace with the WS Addressing namespace

    Hi

    I need to implement a webservice with WSSE and WSAddressing support.
    Since I am using WSSE encryption on the SOAP Body element level, I could not use the @PayloadRoot because Spring would not...
  3. Possible solution for this problem: SWS-519

    This is more a follow up on my question earlier posted...

    I Googled my way through https://jira.springsource.org/browse/SWS-519 where I learned that someone had already submitted a patch for...
  4. Wss4jSecurityInterceptor 's handleFault: not programmed to return a secured message

    Hi

    I secured my webservices with WSSE Signature, Timestamp and Encryption. I have noticed that my response messages are not encrypted or signed when a (XSD) validation error occurs.

    I checked...
  5. WS-Security Encryption applied the whole SOAP env Body won't work in Spring WS 2.0.1

    I have deployed my webservice implemented (with the usual @Endpoint, @tPayloadRoot, @,ResponsePayload, @RequestPayload annotations). When I am not enforcing WS-Security Encryption everything seems to...
Results 1 to 5 of 5