Note: This bug is displayed in read-only format because the product is no longer active in Red Hat Bugzilla.

Bug 913411

Summary:	SOAPFaultException cannot render SOAP 1.2 Fault Subcode in CXF
Product:	[JBoss] JBoss Enterprise Application Platform 6	Reporter:	Tadayoshi Sato <tasato>
Component:	Web Services	Assignee:	Alessio Soldano <asoldano>
Status:	CLOSED CURRENTRELEASE	QA Contact:
Severity:	urgent	Docs Contact:
Priority:	urgent
Version:	6.0.1	CC:	atangrin, cdewolf, ehugonne, jawilson, myarboro, psakar, rsvoboda, smumford
Target Milestone:	ER4
Target Release:	EAP 6.1.1
Hardware:	Unspecified
OS:	Unspecified
URL:	https://issues.jboss.org/browse/WFLY-1667
Whiteboard:
Fixed In Version:		Doc Type:	Bug Fix
Doc Text:		Story Points:	---
Clone Of:		Environment:
Last Closed:	2013-09-16 20:21:54 UTC	Type:	Bug
Regression:	---	Mount Type:	---
Documentation:	---	CRM:
Verified Versions:		Category:	---
oVirt Team:	---	RHEL 7.3 requirements from Atomic Host:
Cloudforms Team:	---	Target Upstream Version:
Embargoed:

Description Tadayoshi Sato 2013-02-21 08:27:00 UTC

Description of problem:
Platform BZ for https://issues.jboss.org/browse/JBWS-3601

Backport https://issues.apache.org/jira/browse/CXF-4790, which is the root cause. The code below doesn't render <soapenv:Subcode>:

  import javax.xml.soap.SOAPConstants;
  import javax.xml.soap.SOAPFactory;
  import javax.xml.soap.SOAPFault;
  import javax.xml.ws.soap.SOAPFaultException;
  ...
    SOAPFactory factory = SOAPFactory.newInstance(SOAPConstants.SOAP_1_2_PROTOCOL);
    SOAPFault fault = factory.createFault("Operator not found", new QName(SOAPConstants.URI_NS_SOAP_1_2_ENVELOPE, "Receiver"));
    fault.appendFaultSubcode(new QName("...", "OperatorNotFound"));
    ...
    throw new SOAPFaultException(fault);

Comment 1 Rostislav Svoboda 2013-02-22 12:04:32 UTC

Fix Versions for CXF-4790 are 2.8.0, 2.7.4, 2.6.7, 2.5.10

EAP 6.1.0 DR4 is using 2.6.6, version 2.6.7 was not yet released

If this should be included in EAP 6.1.0, jboss-eap-6.1.0 flag must be selected to enter 3-ACK process.

Comment 9 JBoss JIRA Server 2013-03-28 10:18:09 UTC

Alessio Soldano <asoldano> made a comment on jira JBWS-3601

From a community point of view, the fix for this is coming in next CXF version. Scheduling for jbossws-cxf-4.2

Comment 11 JBoss JIRA Server 2013-04-05 16:35:14 UTC

Alessio Soldano <asoldano> updated the status of jira JBWS-3601 to Resolved

Comment 12 JBoss JIRA Server 2013-04-05 16:35:14 UTC

Alessio Soldano <asoldano> made a comment on jira JBWS-3601

Solving this upstream jira as a consequence of having moved to cxf 2.7.4

Comment 13 mark yarborough 2013-06-04 21:31:23 UTC

Was proposed or approved for 6.1.0 but did not make it into the payload, so setting jboss-eap-6.1.0- (for history) and jboss-eap-6.1.1? (to try again)

Comment 14 Carlo de Wolf 2013-07-08 09:55:54 UTC

ER3 contains 2.6.8 which has supposedly fixed the issue.

Comment 15 Emmanuel Hugonnet (ehsavoie) 2013-07-10 10:24:11 UTC

Looks like this is not enough with EJB exposed as webservices.

Comment 16 Emmanuel Hugonnet (ehsavoie) 2013-07-11 07:26:53 UTC

PR: https://github.com/jbossas/jboss-eap/pull/236

Comment 18 Petr Sakař 2013-08-07 12:43:02 UTC

Verified by running test against EAP-6.1.1.ER3 (failed) and EAP-6.1.1.ER4 (passed)

References
Upstream test in 4.2 https://source.jboss.org/changelog/JBossWS?cs=17768
EAP6.1 test https://github.com/jbossas/jboss-eap/pull/236

Procedure
git clone git clone https://github.com/jbossas/jboss-eap.git
cd jboss-eap
git tags -l
git checkout tags/EAP_6.1.1.ER4
start-as #EAP_6.1.1.ER4
mvn -s tools/maven/conf/settings.xml test -Dts.basic -Dtest=org.jboss.as.test.integration.ws.basic.*TestCase -pl :jboss-as-ts-integ-basic
#tests passed#
stop-as
start-as #EAP_6.1.1.ER3 previous version
mvn -s tools/maven/conf/settings.xml test -Dts.basic -Dtest=org.jboss.as.test.integration.ws.basic.*TestCase -pl :jboss-as-ts-integ-basic
#test failed#

Comment 20 Scott Mumford 2013-08-29 03:57:55 UTC

Marking for exclusion from the 6.1.1 Release Notes document as an entry for this bug could not be completed or verified in time.

Comment 22 JBoss JIRA Server 2013-10-21 14:05:30 UTC

Alessio Soldano <asoldano> updated the status of jira JBWS-3601 to Closed