fix up pointers to related specs

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

spec/src/main/asciidoc/appC-bibliography.adoc

@@ -28,8 +28,8 @@ http://www.w3.org/TR/2001/NOTE-wsdl-20010315.
 - [[[bib6,6]]] Rahul Sharma. The Java API for XML Based RPC (JAX-RPC) 1.0. JSR, JCP, June 2002. See
 http://jcp.org/en/jsr/detail?id=101.
 
-- [[[bib7,7]]] Roberto Chinnici. The Java API for XML Based RPC (JAX-RPC) 1.1. Maintenance JSR, JCP,
-August 2003. See http://jcp.org/en/jsr/detail?id=101.
+- [[[bib7,7]]] Jakarta XML RPC Specification 1.1. Eclipse Foundation, September 2019. See
+https://jakarta.ee/specifications/xml-rpc/.
 
 - [[[bib8,8]]] Keith Ballinger, David Ehnebuske, Martin Gudgin, Mark Nottingham, and Prasad Yendluri. Basic
 Profile Version 1.0. Final Material, WS-I, April 2004. See
@@ -57,17 +57,17 @@ Working Draft, W3C, August 2004. See http://www.w3.org/TR/2004/WD-wsdl20-2004080
 - [[[bib15,15]]] Joshua Bloch. A Metadata Facility for the Java Programming Language. JSR, JCP, August 2003. See
 http://jcp.org/en/jsr/detail?id=175.
 
-- [[[bib16,16]]] Jim Trezzo. Web Services Metadata for the Java Platform. JSR, JCP, August 2003. See
-http://jcp.org/en/jsr/detail?id=181.
+- [[[bib16,16]]] Jakarta XML Web Services Metadata Specification 3.0. Eclipse Foundation, November 2020. See
+https://jakarta.ee/specifications/web-services-metadata.
 
-- [[[bib17,17]]] Jim Knutson and Heather Kreger. Web Services for J2EE. JSR, JCP, September 2002. See
+- [[[bib17,17]]] Jakarta Enterprise. Web Services Specification. Eclipse Foundation, November 2020. See
 http://jcp.org/en/jsr/detail?id=109.
 
 - [[[bib18,18]]] Nataraj Nagaratnam. Web Services Message Security APIs. JSR, JCP, April 2002. See
 http://jcp.org/en/jsr/detail?id=183.
 
-- [[[bib19,19]]] Farrukh Najmi. Java API for XML Registries 1.0 (JAXR). JSR, JCP, June 2002. See
-http://www.jcp.org/en/jsr/detail?id=93.
+- [[[bib19,19]]] Jakarta XML Registries Specification 1.0. Eclipse Foundation, September 2019. See
+https://jakarta.ee/specifications/xml-registries.
 
 - [[[bib20,20]]] Keith Ballinger, David Ehnebuske, Chris Ferris, Martin Gudgin, Canyang Kevin Liu, Mark
 Nottingham, Jorgen Thelin, and Prasad Yendluri. Basic Profile Version 1.1. Final Material, WS-I,
@@ -132,3 +132,6 @@ Recommendation, W3C, May 2006. See http://www.w3.org/TR/2006/REC-ws-addr-soap-20
 
 - [[[bib38,38]]] John Barton, Satish Thatte, and Henrik Frystyk Nielsen. SOAP Messages With Attachments. Note,
 W3C, December 2000. http://www.w3.org/TR/SOAP-attachments.
+
+- [[[bib39,39]]] Jakarta XML Binding Specification 3.0. Eclipse Foundation, November 2020. See
+https://jakarta.ee/specifications/xml-binding.

spec/src/main/asciidoc/ch01-introduction.adoc

@@ -21,11 +21,11 @@ considered the de-facto service description language for XML Web
 Services.
 
 JAX-RPC 1.0<<bib6>> defined APIs and conventions for supporting RPC
-oriented XML Web Services in the Java platform. JAX-RPC 1.1<<bib7>> added
-support for the WS-I Basic Profile 1.0<<bib8>> to improve interoperability between JAX-RPC
-implementations and with services implemented using other technologies.
+oriented XML Web Services in the Java platform. Jakarta XML RPC<<bib7>> added
+support for the WS-I Basic Profile 1.0<<bib8>> to improve interoperability between
+Jakarta XML RPC implementations and with services implemented using other technologies.
 
-Jakarta XML Web Services (this specification) is a follow-on to JAX-RPC 1.1,
+Jakarta XML Web Services (this specification) is a follow-on to Jakarta XML RPC,
 extending it as described in the following sections.
 
 Throughout the document, references to JAXB refer to the Jakarta XML Binding
@@ -45,9 +45,9 @@ Due primarily to scheduling concerns, JAX-RPC 1.0 defined its own data
 binding facilities. With the release of JAXB 1.0 <<bib9>>
 there is no reason to maintain two separate sets of XML mapping
 rules in the Java platform. Jakarta XML Web Services will delegate data
-binding-related tasks to the Jakarta XML Binding<<bib10>>
+binding-related tasks to the Jakarta XML Binding<<bib39>>
 specification that is being developed in parallel with Jakarta XML Web Services. +
-Jakarta XML Binding<<bib10>> will add support for Java to XML
+Jakarta XML Binding<<bib39>> will add support for Java to XML
 mapping, additional support for less used XML schema constructs, and
 provide bidirectional customization of Java
 &#x21d4; XML data binding. Jakarta XML Web Services will allow
@@ -56,7 +56,7 @@ and optional schema validation.
 * JAX-WS 2.1 requires JAXB 2.1<<bib11>>.
 * JAX-WS 2.2 requires JAXB 2.2<<bib12>>.
 * JAX-WS 2.3 requires JAXB 2.3<<bib13>>.
-* Jakarta XML Web Services 3.0 requires Jakarta XML Binding 3.0.
+* Jakarta XML Web Services 3.0 requires Jakarta XML Binding 3.0<<bib39>>.
 
 SOAP 1.2::
 Whilst SOAP 1.1 is still widely deployed, it’s expected that services
@@ -78,7 +78,7 @@ Jakarta XML Web Services specification._
 ====
 
 WS-I Basic Profile 1.1::
-JAX-RPC 1.1 added support for WS-I Basic Profile 1.0. WS-I Basic
+Jakarta XML RPC added support for WS-I Basic Profile 1.0. WS-I Basic
 Profile 1.1 is expected to supersede 1.0 during the lifetime of this
 specificatoin and Jakarta XML Web Services will add support
 for the additional clarifications it provides.
@@ -121,7 +121,7 @@ Jakarta XML Web Services will simplify client and service access
 to the messages underlying an exchange.
 
 Session Management::
-JAX-RPC 1.1 session management capabilities are tied to HTTP. Jakarta
+Jakarta XML RPC session management capabilities are tied to HTTP. Jakarta
 XML Web Services will add support for message based session management.
 
 Jakarta XML Web Services will also address issues that have arisen
@@ -142,11 +142,11 @@ the burden on developers when creating new versions of existing services.
 The following are non-goals:
 
 Backwards Compatibility of Binary Artifacts::
-Binary compatibility between JAX-RPC 1.x and Jakarta XML Web Services
+Binary compatibility between Jakarta XML RPC and Jakarta XML Web Services
 implementation runtimes.
 
 Pluggable data binding::
-Jakarta XML Web Services will defer data binding to Jakarta XML Binding<<bib10>>;
+Jakarta XML Web Services will defer data binding to Jakarta XML Binding<<bib39>>;
 it is not a goal to provide a plug-in API to allow other types of data
 binding technologies to be used in place of Jakarta XML Binding. However,
 Jakarta XML Web Services will maintain the capability to selectively disable
@@ -158,19 +158,19 @@ Use of the SOAP encoding is essentially deprecated in the web services
 community, e.g., the WS-I Basic Profile<<bib8>> excludes SOAP encoding. Instead,
 literal usage is  preferred, either in the RPC or document style. +
  +
-SOAP 1.1 encoding is supported in JAX-RPC 1.0 and 1.1 but its support
+SOAP 1.1 encoding is supported in JAX-RPC 1.0 and Jakarta XML RPC but its support
 in Jakarta XML Web Services runs counter to the goal of delegation of
 data binding to Jakarta XML Binding. Therefore Jakarta XML Web Services
 will make support for SOAP 1.1 encoding optional and defer description of
-it to JAX-RPC 1.1. +
+it to Jakarta XML RPC. +
  +
 Support for the SOAP 1.2 Encoding<<bib4>>
 is optional in SOAP 1.2 and Jakarta XML Web Services will not add
 support for SOAP 1.2 encoding.
 
 Backwards Compatibility of Generated Artifacts::
 JAX-RPC 1.0 and JAXB 1.0 bind XML to Java in different ways.
-Generating source code that works with unmodified JAX-RPC 1.x client
+Generating source code that works with unmodified Jakarta XML RPC client
 source code is not a goal.
 
 Support for Java versions prior to Java SE 5.0::
@@ -181,7 +181,7 @@ Services on Java versions prior to Java SE 5.0.
 Service Registration and Discovery::
 It is not a goal of Jakarta XML Web Services to describe registration
 and discovery of services via UDDI or ebXML RR. This capability is
-provided independently by JAXR<<bib19>>.
+provided independently by Jakarta XML Registries<<bib19>>.
 
 [[requirements]]
 === Requirements
@@ -190,7 +190,7 @@ provided independently by JAXR<<bib19>>.
 ==== Relationship To Jakarta XML Binding
 
 Jakarta XML Web Services specification describes the WSDL &#x21d4; Java mapping,
-but data binding is delegated to Jakarta XML Binding<<bib10>>. The
+but data binding is delegated to Jakarta XML Binding<<bib39>>. The
 specification must clearly designate where Jakarta XML Binding rules
 apply to the WSDL &#x21d4; Java mapping without reproducing those
 rules and must describe how Jakarta XML Binding capabilities (e.g.,
@@ -223,15 +223,15 @@ The specification must provide a standard way to customize the WSDL
 methods will be specified:
 
 Java Annotations::
-In conjunction with Jakarta XML Binding<<bib10>> and Jakarta XML
+In conjunction with Jakarta XML Binding<<bib39>> and Jakarta XML
 Web Services Metadata<<bib16>> specifications,
 the specification will define a set of standard annotations
 that may be used in Java source files to specify the mapping from Java
 artifacts to their associated WSDL components. The annotations will
 support mapping to WSDL 1.1.
 
 WSDL Annotations::
-In conjunction with Jakarta XML Binding<<bib10>> and Jakarta XML
+In conjunction with Jakarta XML Binding<<bib39>> and Jakarta XML
 Web Services Metadata<<bib16>> specifications,
 the specification will define a set of standard annotations
 that may be used either within WSDL documents or as in an external

spec/src/main/asciidoc/ch02-wsdl_to_java_mapping.adoc

@@ -46,7 +46,7 @@ the source WSDL document and the applicable external binding files.
 
 A WSDL document has a root `wsdl:definitions` element. A
 `wsdl:definitions` element and its associated `targetNamespace`
-attribute is mapped to a Java package. Jakarta XML Binding<<bib10>>
+attribute is mapped to a Java package. Jakarta XML Binding<<bib39>>
 (see appendix D) defines a standard mapping from a namespace URI to a
 Java package name. By default, this algorithm is used to map the value
 of a `wsdl:definitions` element’s `targetNamespace` attribute to a Java
@@ -55,7 +55,7 @@ package name.
 &#9674; _Conformance (Definitions mapping):_ In the absence of customizations,
 the Java package
 name is mapped from the value of a `wsdl:definitions` element’s
-`targetNamespace` attribute using the algorithm defined by Jakarta XML Binding<<bib10>>.
+`targetNamespace` attribute using the algorithm defined by Jakarta XML Binding<<bib39>>.
 
 An application MAY customize this mapping using the `jaxws:package`
 binding declaration defined in <<bindingdecldefinitions>>.
@@ -809,8 +809,8 @@ class MyPriceHandler implements AsyncHandler<Float> {
 [[wsdl11typemapping]]
 === Types
 
-Mapping of XML Schema types to Java is described by the JAXB 2.1
-specification<<bib11>>. The contents of a `wsdl:types` section is
+Mapping of XML Schema types to Java is described by the Jakarta XML Binding
+specification<<bib39>>. The contents of a `wsdl:types` section is
 passed to Jakarta XML Binding along with any additional type or element declarations
 (e.g., see <<wsdl11asyncmethod>>) required to map other WSDL
 constructs to Java. E.g., <<wsdl11asyncmethod>> defines an
@@ -1062,7 +1062,7 @@ WSDL 1.1 MIME binding<<bib5>>:
   A binding construct that may be used to bind a message part to an
   attachment.
 
-Jakarta XML Binding<<bib10>> describes the mapping from the WS-I
+Jakarta XML Binding<<bib39>> describes the mapping from the WS-I
 defined `wsiap:swaref` schema type to Java and, since Jakarta XML Web Services inherits
 this capability, it is not discussed further here. Use of the
 `mime:content` construct is outside the scope of Jakarta XML Binding mapping and the
@@ -1098,7 +1098,7 @@ set of MIME types described for the part in the binding. The case where
 the parameter mode is `INOUT` and is bound to different mime bindings in
 the input and output messages using the `mime:content` element MUST also
 be treated in the same way as described above. Please refer to appendix
-H in the Jakarta XML Binding specification <<bib10>> for details
+H in the Jakarta XML Binding specification <<bib39>> for details
 of the type mapping.
 
 The part belongs to the message bound by the `soap:body` then it is
@@ -1396,7 +1396,7 @@ mapped from the WSDL port type for both referenced bindings.
 [[xmlnames]]
 === XML Names
 
-Appendix D of Jakarta XML Binding<<bib13>> defines a mapping from
+Appendix D of Jakarta XML Binding<<bib39>> defines a mapping from
 XML names to Java identifiers. Jakarta XML Web Services uses this mapping to convert WSDL
 identifiers to Java identifiers with the following modifications and
 additions:

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

@@ -133,7 +133,7 @@ following criteria:
 * `jakarta.jws.WebMethod` if used, MUST NOT have the `exclude` element set
 to `true`.
 * All method parameters and return types are compatible with the Jakarta
-XML Binding<<bib10>> Java to XML Schema mapping definition
+XML Binding<<bib39>> Java to XML Schema mapping definition
 
 &#9674; _Conformance (portType naming):_ The `jakarta.jws.WebService` annotation (see section
 <<mdwebservice>>) MAY be used to customize the `name` and

spec/src/main/asciidoc/ch05-service_apis.adoc

@@ -469,7 +469,7 @@ applications._
 ====
 
 A generated contract MUST follow the rules in <<j2wsdl11chap>> and
-those in the Jakarta XML Binding specification <<bib10>>.
+those in the Jakarta XML Binding specification <<bib39>>.
 
 [[contractproviderendpoints]]
 ===== Provider-based Endpoints