SlideServe
Télécharger Obtenir Pro
Menu
Accueil Pro
Préférences
ApparenceLight Aide et commentaires
© SlideServe · v2026

Enhancing Fault Message Design in WSDL for Improved Automated Service Interactions

wiley avatar
wiley
12 diapositives · 247 Views · Oct 13, 2014

This document discusses the motivation and methodology for defining structured fault messages in WSDL, enabling service requesters to automatically interpret and adapt to faults without human intervention. By establishing a standard base for fault messages, interface designers can create rich, descriptive fault types that assist in fault handling. Key elements include defining a base set of fault information, extending it for specialized faults, and refining fault descriptions. Specific examples illustrate the application of these concepts in WSDL operations, enhancing the overall robustness and usability of web services.

Enhancing Fault Message Design in WSDL for Improved Automated Service Interactions - slide 1
01 / 12Enhancing Fault Message Design in WSDL for Improved Automated Service Interactions
1 / 17

Télécharger la présentation

Enhancing Fault Message Design in WSDL for Improved Automated Service Interactions
Une image / un lien ci-dessous est fourni (tel quel) pour télécharger la présentation

Politique de téléchargement : le contenu du site vous est fourni TEL QUEL pour votre information et votre usage personnel ; il ne peut être vendu, concédé sous licence ni partagé sur d’autres sites sans l’accord de son auteur.Le contenu vous est fourni TEL QUEL, pour votre information et votre usage personnel uniquement. Téléchargez la présentation en cliquant sur ce lien. Lors du téléchargement, si vous ne parvenez pas à télécharger une présentation, l’éditeur a peut-être supprimé le fichier de son serveur.Pendant le téléchargement, si vous ne parvenez pas à obtenir une présentation, le fichier a peut-être été supprimé par l’éditeur.

F I N

Plus de contenu associé

Transcription de la présentation

  1. WS-BaseFaults Steve Tuecke Globus Alliance @ Argonne tuecke@mcs.anl.gov

  2. Motivation • WSDL request-response operations allow for zero or more “fault” messages • Allowing service requesters to automatically (without human intervention) understand and/or adapt to faults requires interface designers to define rich, structured fault messages • Standard fault messages encourage tooling that can assist interface designers, service implementers, and client implementers

  3. Approach • Define base set of information that can appear in fault messages • Convention for how to extend this base fault type for more specialized faults • Refine the type of the fault • Add information relevant to that refined fault type • Convention for using these extended fault element as WSDL 1.1 fault messages

  4. BaseFault Element <BaseFault> <-- type=BaseFaultType --> <Timestamp>xsd:dateTime</Timestamp> <OriginatorReference> wsa:EndpointReferenceType </OriginatorReference> ? <ErrorCode dialect="anyURI">xsd:string</ErrorCode> ? <Description>xsd:string</Description> * <FaultCause>wsbf:BaseFault</FaultCause> * </BaseFault>

  5. BaseFaultType Fields (1) • Timestamp (required): Time at which the fault occurred • OriginatorReference (optional): WS-Addressing EndpointReference of the WS that generated the fault • Can omit if it is clearly implied • Useful particularly with FaultCause • ErrorCode (optional): String error code for supporting legacy fault reporting systems • @dialect: URI specifying context of string

  6. BaseFaultType Fields (2) • Description (0..unbounded): Plain language description(s) of the fault • Use with xsi:lang • FaultCause (0..unbounded): BaseFault element(s) that describes the underlying cause of this fault.

  7. Using BaseFaultType • For each distinct fault on WSDL operation • Define XSD complexType that extends BaseFaultType • Represents the fault’s distinct type • May not define any additional fields • Define XSD element with this extended fault type • Define WSDL message using this fault element • Define WSDL operation fault element using this messag

  8. Example (1) <wsdl:portType name=“ServiceGroupRegistration” …> <wsdl:operation name="Add"> <wsdl:input name="AddRequest“ message="wssg:AddRequest"/> <wsdl:output name="AddResponse" message="wssg:AddResponse"/> <wsdl:fault name="UnsupportedMemberInterfaceFault" message="wssg:UnsupportedMemberInterfaceFault"/> <wsdl:fault name="AddRefusedFault" message="wssg:AddRefusedFault"/> </wsdl:operation> </wsdl:portType>

  9. Example (2) <wsdl:message name="AddRefusedFault"> <wsdl:part name="AddRefusedFault" element="wssg:AddRefusedFault" /> </wsdl:message> <xsd:complexType name="AddRefusedFaultType"> <xsd:complexContent> <xsd:extension base="wsbf:BaseFaultType"/> </xsd:complexContent> </xsd:complexType> <xsd:element name="AddRefusedFault" type="wssg:AddRefusedFaultType"/>

  10. Example (3) <xsd:complexType name=“ExceededMaxSizeFaultType"> <xsd:complexContent> <xsd:extension base="wsbf:AddRefusedFaultType"> <xsd:sequence> <xsd:element name=“maxSize” type=“xsd:integer”\> </xsd:sequence> </xsd:extension> </xsd:complexContent> </xsd:complexType> <xsd:element name=“ExceededMaxSizeFault" type="wssg:ExceededMaxSizeFaultType"/>

  11. Binding to JAX-RPC • Using XSD type extension to model fault type hierarchies results in appropriate Java object type hierarchies • Java exception catch blocks can match on this type hierarchy

  12. Binding to SOAP • WS-BaseFaults only specifies what is done at WSDL 1.1 abstract interface (portType) level • Intended for defining service/application faults • Binding a fault message to SOAP is the purview of a WSDL binding definition • Use standard WSDL 1.1  SOAP 1.1 binding • Issue: Some redundancy between WS-BaseFault information and SOAP 1.2 faults • May want some changes to WS-BaseFaults for WSDL 2.0 and its SOAP 1.2 binding