What does the <service-name-pattern> element in the following set of XML statements do:
A.
Applies the handlers specified in the <handler-chain> element to all the services with targetNamespace http://example.com/handlers.
B.
Applies the handlers specified in the <handler-chain> element to all services whose name is Hello*.
C.
Applies the handlers specified in the <handler-chain> element to all services whose names begin with Hello.
D.
Applies the handlers in the specified in the <handler-chain> element to the service whose name begins with Hello and targetNamespace is http://example.com/handlers.
https://docs.oracle.com/cd/E17802_01/webservices/webservices/docs/2.0/jaxws/handlers.html
Multiple handler-chain elements may exist within the handler-chains element. These may optionally use a service name, port name, or protocol pattern in their description to apply some chains to certain ports and protocols and not to others. For instance (note the wildcard character used in the service name):
ns1:My*Service
…
ns1:HelloPort
…
##SOAP11_HTTP
…
Handlers will appear in the final handler chain in the order that they are included in the customization file. However, logical handlers will be sorted out and called before protocol handlers during execution.
Starting from a Java class, annotations are used to describe the handler chain as defined by JSR 181. The following example uses the @HandlerChain annotation to refer to a file describing the chain. Note that the chain name must be the empty string.
import javax.jws.HandlerChain;
import javax.jws.WebService;
@WebService
@HandlerChain( file=”handlers.xml”, name=””)
public class MyServiceImpl {
// implementation of class
}