0 Replies Latest reply on Jul 3, 2008 10:23 AM by Fabio Ferrante

    JBossWS, Websphere 5.1 WS-Security interoperability

    Fabio Ferrante Newbie

      I'm developing a webservice client using jbossws native stack v2.0.4 that interact with a web service deployed in websphere 5.1. Authentication was managed by ws-security username profile. By the way, webspehere ws-security implementation was based on draft 13 of ws-security standard while jbossws implements final specs. The result was the following error:

      16:14:16,093 INFO [STDOUT] 16:14:16,078 WARN DefaultExceptionHandler:90 - Unhandled exception caught by the Stripes default exception handler.
      javax.xml.ws.soap.SOAPFaultException: com.ibm.wsspi.wssecurity.SoapSecurityException: The Application Server expected a Security header with the http://schemas.xmlsoap.org/ws/2003/06/secext or http://schemas.xmlsoap.org/ws/2002/07/secext or http://schemas.xmlsoap.org/ws/2002/04/secext namespace, but it was not found.
      at org.jboss.ws.core.jaxws.SOAPFaultHelperJAXWS.getSOAPFaultException(SOAPFaultHelperJAXWS.java:72)
      at org.jboss.ws.core.jaxws.binding.SOAP11BindingJAXWS.throwFaultException(SOAP11BindingJAXWS.java:109)
      at org.jboss.ws.core.CommonSOAPBinding.unbindResponseMessage(CommonSOAPBinding.java:579)
      at org.jboss.ws.core.CommonClient.invoke(CommonClient.java:380)
      at org.jboss.ws.core.jaxws.client.ClientImpl.invoke(ClientImpl.java:302)
      at org.jboss.ws.core.jaxws.client.ClientProxy.invoke(ClientProxy.java:172)
      at org.jboss.ws.core.jaxws.client.ClientProxy.invoke(ClientProxy.java:152)

      So, I can:
      - suggest an upgrade of websphere to v6 (not possible!!!)
      - use websphere webservice gateway (8()
      - downgrade to draft 13 ws-security specs used by jbossws (is possible?)
      - generate ws-security tag via a custom handler (is possible?)
      - any other ideas?