J2EE 5.0 simpleType service-ref

Type Heirarchy
{http://www.w3.org/2001/XMLSchema}string (by restriction) {http://www.w3.org/2001/XMLSchema}normalizedString (by restriction) {http://www.w3.org/2001/XMLSchema}token (by restriction) {http://java.sun.com/xml/ns/javaee}service-ref_qname-pattern

Type Heirarchy

{http://www.w3.org/2001/XMLSchema}string (by restriction)

{http://www.w3.org/2001/XMLSchema}normalizedString (by restriction)

{http://www.w3.org/2001/XMLSchema}token (by restriction)

{http://java.sun.com/xml/ns/javaee}service-ref_qname-pattern

Target Namespace	http://java.sun.com/xml/ns/javaee
Declared Namespaces	xmlns:javaee=http://java.sun.com/xml/ns/javaee xmlns:xsd=http://www.w3.org/2001/XMLSchema xmlns=http://www.w3.org/2001/XMLSchema

Target Namespace

http://java.sun.com/xml/ns/javaee

Declared Namespaces

xmlns:javaee=http://java.sun.com/xml/ns/javaee
xmlns:xsd=http://www.w3.org/2001/XMLSchema
xmlns=http://www.w3.org/2001/XMLSchema

<xsd:simpleType name="service-ref_qname-pattern">
    <xsd:annotation>
        <xsd:documentation>
This is used to specify the QName pattern in the
attribute service-name-pattern and port-name-pattern in
the handler-chain element

For example, the various forms acceptable here for
service-name-pattern attribute in handler-chain element
are :

Exact Name: service-name-pattern="ns1:EchoService"

In this case, handlers specified in this
handler-chain element will apply to all ports with
this exact service name. The namespace prefix must
have been declared in a namespace declaration
attribute in either the start-tag of the element
where the prefix is used or in an an ancestor
element (i.e. an element in whose content the
prefixed markup occurs)

Pattern : service-name-pattern="ns1:EchoService*"

In this case, handlers specified in this
handler-chain element will apply to all ports whose
Service names are like EchoService1, EchoServiceFoo
etc. The namespace prefix must have been declared in
a namespace declaration attribute in either the
start-tag of the element where the prefix is used or
in an an ancestor element (i.e. an element in whose
content the prefixed markup occurs)

Wild Card : service-name-pattern="*"

In this case, handlers specified in this handler-chain
element will apply to ports of all service names.

The same can be applied to port-name attribute in
handler-chain element.
        </xsd:documentation>
    </xsd:annotation>
    <xsd:restriction base="xsd:token">
        <xsd:pattern value="\*|([\i-[:]][\c-[:]]*:)?[\i-[:]][\c-[:]]*\*?"/>
    </xsd:restriction>
</xsd:simpleType>

This is used to specify the QName pattern in the attribute service-name-pattern and port-name-pattern in the handler-chain element For example, the various forms acceptable here for service-name-pattern attribute in handler-chain element are : Exact Name: service-name-pattern="ns1:EchoService" In this case, handlers specified in this handler-chain element will apply to all ports with this exact service name. The namespace prefix must have been declared in a namespace declaration attribute in either the start-tag of the element where the prefix is used or in an an ancestor element (i.e. an element in whose content the prefixed markup occurs) Pattern : service-name-pattern="ns1:EchoService*" In this case, handlers specified in this handler-chain element will apply to all ports whose Service names are like EchoService1, EchoServiceFoo etc. The namespace prefix must have been declared in a namespace declaration attribute in either the start-tag of the element where the prefix is used or in an an ancestor element (i.e. an element in whose content the prefixed markup occurs) Wild Card : service-name-pattern="*" In this case, handlers specified in this handler-chain element will apply to ports of all service names. The same can be applied to port-name attribute in handler-chain element.

simpleType {http://java.sun.com/xml/ns/javaee}service-ref_qname-pattern

Source

Documentation