Announcement Announcement Module
Collapse
No announcement yet.
PayloadRootQNameEndpointMapping- Wss4jSecurityInterceptor- AxiomSoapMessageFactory Page Title Module
Move Remove Collapse
X
Conversation Detail Module
Collapse
  • Filter
  • Time
  • Show
Clear All
new posts

  • PayloadRootQNameEndpointMapping- Wss4jSecurityInterceptor- AxiomSoapMessageFactory

    Hi

    Does the spring-ws support PayloadRootQNameEndpointMapping with Wss4jSecurityInterceptor with org.springframework.ws.soap.axiom.AxiomSoapMessage Factory

    Because above configuration causes error for me like,
    Code:
    <<||2013-07-14 09:40:20,353||http-apr-8080-exec-7|DEBUG|org.springframework.security.providers.ProviderManager:190||||>> Authentication attempt using org.springframework.security.providers.dao.DaoAuthenticationProvider 
    <<||2013-07-14 09:40:20,357||http-apr-8080-exec-7|DEBUG|org.springframework.ws.soap.security.wss4j.callback.SpringPlainTextPasswordValidationCallbackHandler:78||||>> Authentication success: org.springframework.security.providers.UsernamePasswordAuthenticationToken@f478c279: Principal: org.springframework.security.userdetails.User@fc52b100: Username: test; Password: [PROTECTED]; Enabled: true; AccountNonExpired: true; credentialsNonExpired: true; AccountNonLocked: true; Granted Authorities: ROLE_ADMIN; Password: [PROTECTED]; Authenticated: true; Details: null; Granted Authorities: ROLE_ADMIN 
    <<||2013-07-14 09:40:20,360||http-apr-8080-exec-7|DEBUG|org.apache.ws.security.WSSecurityEngine:343||||>> processHeader: total 193, prepare 1, handle 192 
    <<||2013-07-14 09:40:20,422||http-apr-8080-exec-7|DEBUG|org.apache.axiom.soap.impl.builder.StAXSOAPModelBuilder:316||||>> Starting to process SOAP 1.1 message 
    <<||2013-07-14 09:40:20,423||http-apr-8080-exec-7|DEBUG|org.apache.axiom.soap.impl.builder.StAXSOAPModelBuilder:273||||>> Build the OMElement Envelope by the StaxSOAPModelBuilder 
    <<||2013-07-14 09:40:20,425||http-apr-8080-exec-7|DEBUG|org.apache.axiom.soap.impl.builder.StAXSOAPModelBuilder:273||||>> Build the OMElement Header by the StaxSOAPModelBuilder 
    <<||2013-07-14 09:40:20,426||http-apr-8080-exec-7|DEBUG|org.apache.axiom.soap.impl.builder.StAXSOAPModelBuilder:273||||>> Build the OMElement Security by the StaxSOAPModelBuilder 
    <<||2013-07-14 09:40:20,426||http-apr-8080-exec-7|DEBUG|org.springframework.ws.server.MessageDispatcher:273||||>> Testing endpoint adapter [org.springframework.ws.server.endpoint.adapter.MessageEndpointAdapter@321dfc5e] 
    <<||2013-07-14 09:40:20,429||http-apr-8080-exec-7|DEBUG|org.apache.axiom.soap.impl.llom.SOAPHeaderImpl:426||||>> org.apache.axiom.soap.SOAPProcessingException: An attempt was made to add a normal OMElement as a child of a SOAPHeader.  This is not supported.  The child should be a SOAPHeaderBlock.
    	at org.apache.axiom.soap.impl.llom.SOAPHeaderImpl.addChild(SOAPHeaderImpl.java:423)
    	at org.apache.axiom.om.impl.llom.OMNodeImpl.<init>(OMNodeImpl.java:74)
    	at org.apache.axiom.om.impl.llom.OMElementImpl.<init>(OMElementImpl.java:104)
    	at org.apache.axiom.om.impl.llom.factory.OMLinkedListImplFactory.createOMElement(OMLinkedListImplFactory.java:94)
    	at org.apache.axiom.soap.impl.builder.StAXSOAPModelBuilder.constructNode(StAXSOAPModelBuilder.java:430)
    	at org.apache.axiom.soap.impl.builder.StAXSOAPModelBuilder.createOMElement(StAXSOAPModelBuilder.java:260)
    	at org.apache.axiom.soap.impl.builder.StAXSOAPModelBuilder.createNextOMElement(StAXSOAPModelBuilder.java:229)
    	at org.apache.axiom.om.impl.builder.StAXOMBuilder.next(StAXOMBuilder.java:250)
    	at org.apache.axiom.om.impl.llom.OMElementImpl.getNextOMSibling(OMElementImpl.java:335)
    	at org.apache.axiom.soap.impl.llom.SOAPEnvelopeImpl.getBody(SOAPEnvelopeImpl.java:170)
    	at org.springframework.ws.soap.axiom.AxiomSoapEnvelope.getBody(AxiomSoapEnvelope.java:59)
    	at org.springframework.ws.soap.AbstractSoapMessage.getSoapBody(AbstractSoapMessage.java:36)
    	at org.springframework.ws.soap.AbstractSoapMessage.getPayloadSource(AbstractSoapMessage.java:46)
    	at org.springframework.ws.support.MarshallingUtils.unmarshal(MarshallingUtils.java:55)
    	at org.springframework.ws.server.endpoint.AbstractMarshallingPayloadEndpoint.unmarshalRequest(AbstractMarshallingPayloadEndpoint.java:143)
    	at org.springframework.ws.server.endpoint.AbstractMarshallingPayloadEndpoint.invoke(AbstractMarshallingPayloadEndpoint.java:129)
    	at org.springframework.ws.server.endpoint.adapter.MessageEndpointAdapter.invoke(MessageEndpointAdapter.java:41)
    	at org.springframework.ws.server.MessageDispatcher.dispatch(MessageDispatcher.java:221)
    	at org.springframework.ws.server.MessageDispatcher.receive(MessageDispatcher.java:168)
    	at org.springframework.ws.transport.support.WebServiceMessageReceiverObjectSupport.handleConnection(WebServiceMessageReceiverObjectSupport.java:88)
    	at org.springframework.ws.transport.http.WebServiceMessageReceiverHandlerAdapter.handle(WebServiceMessageReceiverHandlerAdapter.java:57)
    Please share if there is any standard way/example for this configuration

    Thanks

  • #2
    Sorry for not getting to this sooner. We are in the process of moving to StackOverflow for our forums.

    This question is probably a better candidate for StackOverflow, perhaps against the #spring-ws tag. If you do post it there, please reply here with the link. Thanks!

    Comment

    Working...
    X