fix invalid references

Signed-off-by: Lukas Jungmann <lukas.jungmann@oracle.com>

spec/src/main/asciidoc/ch03-java_to_wsdl_mapping.adoc

@@ -1150,7 +1150,7 @@ Each method in a Java SEI is mapped to a `soap:operation` child element
 of the corresponding `wsdl:operation`. The value of the `style`
 attribute of the `soap:operation` is `document` or `rpc`. If not
 specified, the value defaults to the value of the `style` attribute of
-the `soap:binding`. WS-I Basic Profile<<8>>
+the `soap:binding`. WS-I Basic Profile<<bib8>>
 requires that all operations within a given SOAP HTTP binding
 instance have the same binding style.
 

spec/src/main/asciidoc/ch07-annotations.adoc

@@ -714,7 +714,7 @@ public @interface Addressing {
 
 The `Addressing` annotation is applied to an endpoint implementation
 class and to an injected web service proxy reference. It is used to
-control the use of WS-Addressing<<bib26>><<37>><<bib27>>.
+control the use of WS-Addressing<<bib26>><<bib37>><<bib27>>.
 It corresponds with the `AddressingFeature` described in <<addressingfeature>>.
 
 [id="Table 7.14"]

spec/src/main/asciidoc/ch09-handler_framwork.adoc

@@ -56,11 +56,11 @@ message. Protocol handlers are handlers that implement any interface
 derived from `jakarta.xml.ws.handler.Handler` except
 `jakarta.xml.ws.handler.LogicalHandler`.
 
-
+[[handarchfig]]
+.Handler architecture
 image::images/handarch.png[]
-Figure 9.1: Handler architecture
 
-Figure <<9.2>> shows the class hierarchy for handlers.
+Figure <<handclshie>> shows the class hierarchy for handlers.
 
 Handlers for protocols other than SOAP are expected to implement a
 protocol-specific interface that extends `jakarta.xml.ws.handler.Handler`.
@@ -80,8 +80,9 @@ destruction of handlers according to the rules specified in section
 management of message contexts according to the rules specified in
 <<handmsgctxmngmt>>
 
+[[handclshie]]
+.Handler class hierarchy
 image::images/handlers.png[]
-Figure 9.2: Handler class hierarchy
 
 &#9674; _Conformance (Logical handler support):_ All binding implementations MUST support
 logical handlers (see <<handlertypes>>) being deployed in their
@@ -173,13 +174,14 @@ handler chain as returned by the `HandlerResolver` for the service in
 use and sorting its elements so that all logical handlers precede all
 protocol handlers. In performing this operation, the order of handlers
 of any given type (logical or protocol) in the original chain is
-maintained. Figure <<9.3>> illustrates this.
+maintained. <<handord>> illustrates this.
 
 <<handlerexecution>> describes how the handler order relates to
 the order of handler execution for inbound and outbound messages.
 
+[[handord]]
+.Handler ordering, Ln and Pn represent logical and protocol handlers respectively.
 image::images/handord.png[]
-Figure 9.3: Handler ordering, Ln and Pn represent logical and protocol handlers respectively.
 
 [[handlerchain]]
 ===== jakarta.jws.HandlerChain annotation
@@ -211,10 +213,11 @@ annotation, the default handler resolver MUST return handler chains
 consistent with the contents of the handler chain descriptor referenced
 by the `HandlerChain` annotation.
 
-Figure <<9.4>> shows an endpoint implementation class annotated
+Figure <<hchainannex>> shows an endpoint implementation class annotated
 with a `HandlerChain` annotation.
 
-[id="9.4"]
+[id="hchainannex"]
+.Use of the HandlerChain annotation
 [source,java,numbered]
 -------------
 @WebService
@@ -223,7 +226,6 @@ public class MyService {
     ...
 }
 -------------
-Figure 9.4: Use of the HandlerChain annotation
 
 [[jakarta.xml.ws.binding]]
 ===== jakarta.xml.ws.Binding
@@ -283,7 +285,7 @@ typically via the `jakarta.annotation.Resource` annotation. After all the
 injections have been carried out, including in the case where no
 injections were requested, the runtime MUST invoke the method carrying a
 `jakarta.annotation.PostConstruct` annotation, if present. Such a method
-MUST satisfy the requirements in JSR-250 <<bib35>> for lifecycle
+MUST satisfy the requirements in Jakarta Annotations <<bib35>> for lifecycle
 methods (i.e. it has a void return type and takes zero arguments). The
 handler instance is then ready for use.
 
@@ -301,7 +303,7 @@ stops using the handler for processing inbound or outbound messages.
 After taking the handler offline, a JAX-WS implementation SHOULD invoke
 the lifecycle method which carries a `jakarta.annotation.PreDestroy`
 annotation, if present, so as to permit the handler to clean up its
-resources. Such a method MUST satisfy the requirements in JSR-250
+resources. Such a method MUST satisfy the requirements in Jakarta Annotations
 <<bib35>> for lifecycle methods
 
 An implementation can only release handlers after the instance they are

spec/src/main/asciidoc/ch10-soap_binding.adoc

@@ -28,7 +28,7 @@ to be configured using annotations or deployment metadata.
 [[soap-roles]]
 ===== SOAP Roles
 
-SOAP 1.1<<bib2>> and SOAP 1.2<<3>><<4>> use different terminology
+SOAP 1.1<<bib2>> and SOAP 1.2<<bib3>><<bib4>> use different terminology
 for the same concept: a SOAP 1.1 _actor_ is equivalent to a SOAP 1.2
 _role_. This specification uses the SOAP 1.2 terminology.
 
@@ -148,7 +148,7 @@ SOAP specific processing as described in the following subsections.
 The SOAP protocol binding performs the following additional processing
 on inbound SOAP messages prior to the start of normal handler invocation
 processing (see <<handlerexecution>>). Refer to the SOAP
-specification<<2>><<3>><<4>> for a normative description of the
+specification<<bib2>><<bib3>><<bib4>> for a normative description of the
 SOAP processing model. This section is not intended to supercede any
 requirement stated within the SOAP specification, but rather to outline
 how the configuration information described above is combined to satisfy
@@ -287,7 +287,7 @@ modify the SOAP message payload.
 [[soapbindprotocols]]
 === SOAP Transport and Transfer Bindings
 
-SOAP<<2>><<4>> can be bound
+SOAP<<bib2>><<bib4>> can be bound
 to multiple transport or transfer protocols. This section describes
 requirements pertaining to the supported protocols for use with SOAP.
 
@@ -299,9 +299,9 @@ The SOAP 1.1 HTTP binding is identified by the URL
 the constant `jakarta.xml.ws.soap.SOAPBinding.SOAP11HTTP_BINDING`.
 
 &#9674; _Conformance (SOAP 1.1 HTTP Binding Support):_ An implementation MUST support the HTTP
-binding of SOAP 1.1<<bib2>> and SOAP With Attachments<<38>> as clarified by the WS-I Basic
+binding of SOAP 1.1<<bib2>> and SOAP With Attachments<<bib38>> as clarified by the WS-I Basic
 Profile<<bib20>>, WS-I Simple SOAP
-Binding Profile<<bib32>> and WS-I Attachment Profile<<33>>.
+Binding Profile<<bib32>> and WS-I Attachment Profile<<bib33>>.
 
 The SOAP 1.2 HTTP binding is identified by the URL
 `http://www.w3.org/2003/05/soap/bindings/HTTP/`, which is also the value