Some Eclipse Foundation services are deprecated, or will be soon. Please ensure you've read this important communication.
Bug 352349 - Soap12 Faultprocessing and Faultcode-Validation
Summary: Soap12 Faultprocessing and Faultcode-Validation
Status: RESOLVED FIXED
Alias: None
Product: z_Archived
Classification: Eclipse Foundation
Component: Eclipselink (show other bugs)
Version: unspecified   Edit
Hardware: PC Windows 7
: P3 normal (vote)
Target Milestone: ---   Edit
Assignee: Nobody - feel free to take it CLA
QA Contact:
URL:
Whiteboard:
Keywords:
Depends on:
Blocks:
 
Reported: 2011-07-18 10:47 EDT by Sven Uhlig CLA
Modified: 2022-06-09 10:24 EDT (History)
2 users (show)

See Also:

Attachments
Add an attachment (proposed patch, testcase, etc.)

Note You need to log in before you can comment on or make changes to this bug.
Description Sven Uhlig CLA 2011-07-18 10:47:37 EDT 
under soap12 (useSOAP12=true) scenario - faultcodes are validated see 
	com.sun.xml.messaging.saaj.soap.ver1_2.Fault1_2Impl#checkIfStandardFaultCode (metro - webservices-rt)
	and http://www.w3.org/TR/soap12-part1/#faultcodes
	
and therefore the processing of faults doesn't work  in 
	org.eclipse.persistence.internal.dbws.ProviderHelper#invoke
Comment 1 David McCann CLA 2012-12-20 14:20:10 EST 
For our purposes, currently we set "Server" and "Client" as fault codes.  Since SOAP 1.2 accepts only 5 fault code values, and neither "Server" or "Client" is in the list, we will use "Receiver" for "Server" and "Sender" for "Client" if we detect SOAP 1.2.
Comment 2 David McCann CLA 2012-12-20 14:33:14 EST 
Fix checked into EclipseLink streams:

2.4.2 (SHA1 ID: 7f39066f68c18f5be5483f3ad00bb19e6267e4ce)
2.5.0 (SHA1 ID: 4fed3114bf174d9373e7fb60a5bbeae2e0fbf429)
Comment 3 Eclipse Webmaster CLA 2022-06-09 10:15:54 EDT 
The Eclipselink project has moved to Github: https://github.com/eclipse-ee4j/eclipselink
Comment 4 Eclipse Webmaster CLA 2022-06-09 10:24:06 EDT 
The Eclipselink project has moved to Github: https://github.com/eclipse-ee4j/eclipselink