This release of JBoss EAP 6 contains a bug that causes a web service that has a WS-Security Signature policy in its WSDL to return an empty HTTP response that has zero-length of content to client when throws a SOAP Fault instead of the actual SOAP Fault.
This issue presents only when Signature policy is in use.
This is expected to be resolved in a future release of the product.
+++ This bug was initially created as a clone of Bug #1110631 +++
Description of problem:
Platform BZ for https://issues.jboss.org/browse/JBWS-3802
Please port CXF-5810, which is the root cause of the issue, to JBoss WS.
When a web service has a WS-Security Signature policy in its WSDL and throws a SOAP Fault, it returns an empty HTTP response that has zero-length of content to client instead of the SOAP Fault.
This happens only with Signature policy and doesn't happen with any other WS-Security policies like UsernameToken, or without WS-Security.
Steps to Reproduce:
1. From the base maven project run:
> mvn clean install jboss-as:deploy
2. Then run:
> mvn clean test -Pjbossas-remote
- The reproducer client gets empty response from the endpoint.
- The reproducer client should get a SOAP Fault from the endpoint.
Created attachment 910271 [details]
Alessio Soldano <email@example.com> updated the status of jira JBWS-3802 to Resolved
wrong issue, reverting.
Verified on 6.3.2.CP.CR1
Alessio Soldano <firstname.lastname@example.org> updated the status of jira JBWS-3802 to Closed