Jakarta Web Services Metadata 2.1

[lukasj]

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

PR#1:

• A directory in the form wombat/x.y where x.y is the release major.minor version, and the directory contains the following.
• Specification PDF in the form of wombat_x.y.pdf
• Specification HTML in the form of wombat_x.y.html
• A specification page named _index.md following the template at:
  https://github.com/jakartaee/specification-committee/blob/master/spec_page_template.md
• For a Release Review, a summary that a Compatible Implementation
  is complete, passes the TCK, and that the TCK includes sufficient
  coverage of the specification. The TCK users guide MUST include
  the instructions to run the compatible implementations used to
  validate the release. Instructions MAY be by reference.
• The URL of the OSSRH staging repository for the api, javadoc:
  https://oss.sonatype.org/content/repositories/staging/jakarta/jws/jakarta.jws-api/2.1.0/
• The URL of the staging directory on downloads.eclipse.org for the proposed EFTL TCK binary:
  http://download.eclipse.org/ee4j/jakartaee-tck/jakartaee8-eftl/promoted/eclipse-xml-ws-tck-2.3.0.zip
• The URL of the compatibility certification request issue:
  Compatibility certification request for Eclipse Metro 2.4.3 jws-api#47

Include the following in PR#2:

• Specification JavaDoc in the wombat/x.y/apidocs directory.

[dblevins]

It appears the staging repo has been deleted:

• https://oss.sonatype.org/content/repositories/staging/jakarta/jws/jakarta.jws-api/1.1.2/

[lukasj]

correct, the version should be 2.1.0 (since the last version on the JCP is 2.1, the spec should say 2.1 instead of 1.1). As this is not critical for the upcoming release, I'm going to update this (and fix all other more or less related PRs) next week.

[netlify]

Deploy preview for jakartaee-specifications ready!

Built with commit a71e7c6

https://deploy-preview-48--jakartaee-specifications.netlify.com

[kwsutter]

Just putting a "hold" tag on this issue since it hasn't been decided whether the jax-ws specs will be part of Jakarta EE 9 or not...

[lukasj]

well, this API in particular is supposed to be part of Java EE8, thus also Jakarta EE8 but for some reason, likely intentionally as the same version exists in Java SE 8, has not been included in the initial release. See ie Java EE 8 spec, table EE.6-1 (pages 159-160), chapter EE.6.27 (page 189) or chapter EE.9.7 (pages 234-235) or equivalents in Jakarta EE 8 spec document; I've found no sentence in the existing specs saying that this can come from Java SE but as long as the API as such is available, it is perhaps fine.

Also note that all these APIs were removed from Java SE 11, so whatever gets decided regarding required Java SE versions has impact on either pruning/adding this and related APIs.

[kwsutter]

Definitely agree with your arguments, @lukasj. If you feel that any of these Specs have to be part of Jakarta EE 9, then please join in the discussion on the Platform dev mailing list. At this point, none of the three APIs related to XML Web Services are being requested to be added back in. Although jax-ws is getting some backing...
https://accounts.eclipse.org/mailing-list/jakartaee-platform-dev
https://www.eclipse.org/lists/jakartaee-platform-dev/msg00839.html
https://www.eclipse.org/lists/jakartaee-platform-dev/msg00838.html

Thanks!

[lukasj]

TODOs: upload refreshed binaries, fix TCK URL

[lukasj]

binaries were refreshed

[kwsutter]

I'm going to approve just to make progress. But, if you have the cycles, it would probably be good to rename your specs to be consistent with the rest of the specs generated for Jakarta EE.

[kwsutter]

• The designated specification committee representative adds this final checklist to the main PR.
• The specification committee representative merges the specification and apidocs PRs.
• The designated specification committee representative calculates the staged EFTL TCK signature and promotes it to the committee download area
  using the https://ci.eclipse.org/jakartaee-spec-committee/job/promote-release/ job.
• The specification project member who created the staging release promotes the specification api jars to maven central. An example release job script can be found here https://wiki.eclipse.org/MavenReleaseScript.
• The EMO updates the specification page with the ballot results.
  This list goes on the committed spec index page.
• The specification project team should go through the merged spec website page to verify all the links are valid.
• The specification project team should approve the compatibility request.
• The compatible implementation project/vendor MUST send an email tck@eclipse.org for approval of the compatible implementation for trademark usage.
• The specification project team should merge any final release branch as appropriate for the branch management for the project.

[lukasj]

@kwsutter unchecked items were done

[kwsutter]

Thanks!