Summary: | DBWSBuilder utility should support SOAP 1.2 messages | ||
---|---|---|---|
Product: | z_Archived | Reporter: | Mike Norman <michael.norman> |
Component: | Eclipselink | Assignee: | Mike Norman <michael.norman> |
Status: | RESOLVED FIXED | QA Contact: | |
Severity: | normal | ||
Priority: | P3 | CC: | eclipselink.dbws-inbox |
Version: | unspecified | Keywords: | Documentation |
Target Milestone: | --- | ||
Hardware: | All | ||
OS: | All | ||
Whiteboard: |
Description
Mike Norman
2009-05-21 14:33:50 EDT
Deleted by Webmaster add boolean 'useSOAP12' to DBWSBuilder public API - which in turn requires changes to Packager, WSDLGenerator and ProviderHelper to ensure that SOAP 1.2 artifacts are used in the appropriate circumstances NB - detecting if a msg is SOAP 1.1 vs. 1.2 is a bit hokey - you look at the Content-Type (starts with "application/soap+xml") and then verify that the Namespace URI for the SOAPEnvelope is "http://www.w3.org/2003/05/soap-envelope" x fix in SVN revision: 4281 Follow-up re: detecting SOAP 1.2 messages - the only reliable way to detect SOAP 1.2 is presence of 2003/05 envelope: the content-type was a red-herring Need to document new feature - DBWSBuilder utility supports new property 'useSOAP12' Mass update to change fixed in target. Mass update to change fixed in target. Mass update to change fixed in target. Mass update to change fixed in target. Reducing closed DBWS bugs from P1/P2 to P3 to better represent priority of fixes across entire 1.2.0 release The Eclipselink project has moved to Github: https://github.com/eclipse-ee4j/eclipselink |