anchor.diff:  this mode of interaction.
   
   `Dispatch` supports two usage modes, identified by the constants
  -`javax.xml.ws.Service.Mode.MESSAGE` and
  -`javax.xml.ws.Service.Mode.PAYLOAD` respectively:
  +`jakarta.xml.ws.Service.Mode.MESSAGE` and
  +`jakarta.xml.ws.Service.Mode.PAYLOAD` respectively:
   
   *_Message_* In this mode, client applications work directly with
   protocol-specific message structures. E.g., when used with a SOAP
  
positive.code: 
  The default binding for an endpoint is the SOAP 1.1/HTTP one.
  
  ==== javax.xml.ws.WebServiceRef
  
  The `WebServiceRef` annotation is used to declare a reference to a Web
  service. It follows the resource pattern exemplified by the
  `javax.annotation.Resource` annotation in JSR-250 [32]. The
  `WebServiceRef` annotation is required to be honored when running on the
  Java EE 5 platform, where it is subject to the common resource injection
  rules described by the platform specification [33].
  
  ==== javax.xml.ws.WebServiceRefs
  
  The `WebServiceRefs` annotation is used to declare multiple references
  to Web services on a single class. It is necessary to work around the
  
negative.code: 
  === WS Annotations
  
  For details, see https://jakarta.ee/specifications/xml-web-services/[Jakarta XML Web Services]
  
  ==== jakarta.xml.ws.ServiceMode
  
  The `ServiceMode` annotation is used to specify the mode for a provider
  class, i.e. whether a provider wants to have access to protocol message
  payloads (e.g. a SOAP body) or the entire protocol messages (e.g. a SOAP
  envelope).
  
  ==== jakarta.xml.ws.WebFault
  
  The `WebFault` annotation is used when mapping WSDL faults to Java
  exceptions, see section 2.5. It is used to capture the name of the fault
  