Greg L. Turnquist

Results 137 issues of Greg L. Turnquist

**[Kevin Strobel](https://jira.spring.io/secure/ViewProfile.jspa?name=kevin92)** opened **[SWS-962](https://jira.spring.io/browse/SWS-962?redirect=false)** and commented When using the class `org.springframework.ws.soap.security.*wss4j2*.Wss4jSecurityInterceptor` with the property `validationActions` set to _NoSecurity_, Spring-WS-Security still tries to validate the message. In the method `setValidationActions`, Apache's...

status: waiting-for-triage

**[chris snow](https://jira.spring.io/secure/ViewProfile.jspa?name=snowch)** opened **[SWS-755](https://jira.spring.io/browse/SWS-755?redirect=false)** and commented Currently, to use WS Seucrity with Spring WS, it seems that you have to write the policy in the wsdl, and then code/configure to...

status: waiting-for-triage

**[miha-](https://jira.spring.io/secure/ViewProfile.jspa?name=miha-)** opened **[SWS-1092](https://jira.spring.io/browse/SWS-1092?redirect=false)** and commented In the spring tutorial, the endpoint method is annotated with `@PayloadRoot`: `@PayloadRoot(localPart = "orderInput", namespace = "http://samples")` This works fine when the soap message is...

status: waiting-for-triage

**[lashakv](https://jira.spring.io/secure/ViewProfile.jspa?name=JIRAUSER50200)** opened **[SWS-1089](https://jira.spring.io/browse/SWS-1089?redirect=false)** and commented Spring WS Reference documentation has mentions of usage of `securementCallbackHandler` which was removed with Wss4j upgrade to 2.1. Reference URL: https://docs.spring.io/spring-ws/docs/3.0.9.RELEASE/reference/#_encryption_and_decryption_2 Documentation should be updated....

type: documentation

**[makaxel](https://jira.spring.io/secure/ViewProfile.jspa?name=JIRAUSER49639)** opened **[SWS-1088](https://jira.spring.io/browse/SWS-1088?redirect=false)** and commented MockWebServiceServer should allow for an expectation to occur multiple times like MockRestServiceServer ( https://github.com/spring-projects/spring-framework/issues/15991 ) --- No further details from [SWS-1088](https://jira.spring.io/browse/SWS-1088?redirect=false)

type: enhancement

**[Krzysztof Gonia](https://jira.spring.io/secure/ViewProfile.jspa?name=kgonia)** opened **[SWS-1087](https://jira.spring.io/browse/SWS-1087?redirect=false)** and commented After calling addHeaderElement method on SoapHeader element changes in header are not reflected document structure.  Code samples: Let's add element to Header ```java SoapHeader...

status: waiting-for-triage

**[Dmitry Belokursky](https://jira.spring.io/secure/ViewProfile.jspa?name=dbelokursky)** opened **[SWS-1083](https://jira.spring.io/browse/SWS-1083?redirect=false)** and commented mvn goal archetype:**create** should be changed  to mvn archetype:**generate** **[https://issues.apache.org/jira/browse/ARCHETYPE-437]** **[http://maven.apache.org/archetype/maven-archetype-plugin/]**   --- **Affects:** 3.0.8 **Reference URL:** https://docs.spring.io/spring-ws/docs/current/reference/#tutorial-creating-project

type: documentation

**[muralidev81](https://jira.spring.io/secure/ViewProfile.jspa?name=muralidev81)** opened **[SWS-1081](https://jira.spring.io/browse/SWS-1081?redirect=false)** and commented https://mvnrepository.com/artifact/com.sun.xml.xws/xws-security/3.0 We encountered below mentioned ClassCastException while processing SAML token from SOAP WSSE header. Its happening when given SAML token is in proper XML format...

status: waiting-for-triage

**[muralidev81](https://jira.spring.io/secure/ViewProfile.jspa?name=muralidev81)** opened **[SWS-1080](https://jira.spring.io/browse/SWS-1080?redirect=false)** and commented https://mvnrepository.com/artifact/com.sun.xml.xws/xws-security/3.0   We observed exceptions around processSAMLToken is eaten inside and not throwing to the caller. Due to this Authentication failed is also treating as successful...

status: waiting-for-triage

**[Amol Khese](https://jira.spring.io/secure/ViewProfile.jspa?name=amolkhese)** opened **[SWS-1077](https://jira.spring.io/browse/SWS-1077?redirect=false)** and commented Spring Soap/HTTP provides a mechanism to handle handleInvalidXmlException by creating custom WebServiceMessageReceiverHandlerAdapter. However in SOAP/JMS implementation there is no such way to customize handleInvalidXmlException...

type: enhancement