8358701: Remove misleading javax.management.remote API doc wording about JMX spec, and historic link to JMXMP

[kevinjwalls]

Doc-only cleanup, not part of the API/spec.

Remove link to the very old reference implementation of JMXMP in the Javadoc. This may misleadingly imply it is a supported part of the JDK.

---

Progress

• Change must be properly reviewed (1 review required, with at least 1 Reviewer)
• Change requires CSR request JDK-8358759 to be approved
• Change must not contain extraneous whitespace
• Commit message must refer to an issue

Issues

• JDK-8358701: Remove misleading javax.management.remote API doc wording about JMX spec, and historic link to JMXMP (Enhancement - P3)
• JDK-8358759: Remove misleading javax.management.remote API doc wording about JMX spec, and historic link to JMXMP (CSR)

Reviewers

• Alan Bateman (@AlanBateman - Reviewer)
• Serguei Spitsyn (@sspitsyn - Reviewer)

Reviewing

Using git

Checkout this PR locally:
$ git fetch https://git.openjdk.org/jdk.git pull/25670/head:pull/25670
$ git checkout pull/25670

Update a local copy of the PR:
$ git checkout pull/25670
$ git pull https://git.openjdk.org/jdk.git pull/25670/head

Using Skara CLI tools

Checkout this PR locally:
$ git pr checkout 25670

View PR using the GUI difftool:
$ git pr show -t 25670

Using diff file

Download this PR as a diff file:
https://git.openjdk.org/jdk/pull/25670.diff

Using Webrev

Link to Webrev Comment

[bridgekeeper]

👋 Welcome back kevinw! A progress list of the required criteria for merging this PR into master will be added to the body of your pull request. There are additional pull request commands available for use with this pull request.

[openjdk]

@kevinjwalls This change now passes all automated pre-integration checks.

ℹ️ This project also has non-automated pre-integration requirements. Please see the file CONTRIBUTING.md for details.

After integration, the commit message for the final commit will be:

8358701: Remove misleading javax.management.remote API doc wording about JMX spec, and historic link to JMXMP

Reviewed-by: alanb, sspitsyn

You can use pull request commands such as /summary, /contributor and /issue to adjust it as needed.

At the time when this comment was updated there had been 75 new commits pushed to the master branch:

• 9982995: 8358819: The first year is not displayed correctly in Japanese Calendar
• 0ef0986: 8359168: Revert stdin.encoding usage in test/hotspot/jtreg/vmTestbase/nsk/jvmti/AttachOnDemand/attach010/attach010Agent00.java
• 610a18e: 8358688: HttpClient: Simplify file streaming in RequestPublishers.FilePublisher
• ... and 72 more: https://git.openjdk.org/jdk/compare/af87035b713f8bfe05a007a4d4670cefc6a6aaf2...master

As there are no conflicts, your changes will automatically be rebased on top of these commits when integrating. If you prefer to avoid this automatic rebasing, please check the documentation for the /integrate command for further details.

➡️ To integrate this PR with the above commit message to the master branch, type /integrate in a new comment.

[openjdk]

@kevinjwalls The following label will be automatically applied to this pull request:

• serviceability

When this pull request is ready to be reviewed, an "RFR" email will be sent to the corresponding mailing list. If you would like to change these labels, use the /label pull request command.

[kevinjwalls]

Existing docs:
https://docs.oracle.com/en/java/javase/24/docs/api/java.management/javax/management/remote/package-summary.html#

New:

[mlbridge]

Webrevs

• 02: Full - Incremental (e3b46cc6)
• 01: Full - Incremental (25c90c77)
• 00: Full (26ffc32e)

[AlanBateman]

/csr

[openjdk]

@AlanBateman has indicated that a compatibility and specification (CSR) request is needed for this pull request.

@kevinjwalls please create a CSR request for issue JDK-8358701 with the correct fix version. This pull request cannot be integrated until the CSR request is approved.

[dfuch]

I wonder if we should keep the first part of the note - without the link. Something like:

 *
 *       <p><u>Note</u>: The historical JMX Remote API specification
 *         also defined an optional part; optional packages implementing
 *         the optional part of the <em>JMX Remote API</em>
 *         are not part of the <em>Java SE Platform</em>.</p>
 *

@AlanBateman do you think that would be helpful to keep?

[AlanBateman]

What would you think about dropping the sentence "The JMX Remote API allows the use of different type of connectors" and drop "User-defined" from the last list item? Doing that makes it much easier to say that the RMI Connector is standard and that other Connectors are possible using using the JMXConnectorFactory. It removes any discussion as to whether there are two or three "difference types".

I think we want "RMI Connector" to link to either RMIConnector or to the java.management.rmi module description.

My concern with having a historical note is that it invites readers to search for these other "interesting" optional parts, and they will be disappointed. If you do have a historical note then I think it need to say more than "are not part of the Java Platform", it will also need to say that they are not included in the JDK.

[dfuch]

OK - let's drop the historical note then.

[kevinjwalls]

What would you think about dropping the sentence "The JMX Remote API allows the use of different type of connectors" and drop "User-defined" from the last list item

Yes that's fine. As is "User-defined connector protocols..." -> "Other connector protocols..."

[AlanBateman]

As is "User-defined connector protocols..." -> "Other connector protocols..."

I think that would be okay.

[kevinjwalls]

Also removing:
" and, optionally, the Generic Connector (not part of this bundle, see note below)."

[dfuch]

LGTM

[kevinjwalls]

While updating, I now see this as problematic:
"The specification of this functionality is completed by Part III of the JMX Specification, version 1.4"
..as it implies these docs are extended by the historical jmx remote spec.

Updating:

[AlanBateman]

Good

[kevinjwalls]

Thanks Daniel and Alan - I have created the CSR.

[sspitsyn]

Looks good.

[kevinjwalls]

/integrate

[openjdk]

Going to push as commit 66535fe.
Since your change was applied there have been 76 commits pushed to the master branch:

• db7af2b: 8349550: Improve SASL random usage
• 9982995: 8358819: The first year is not displayed correctly in Japanese Calendar
• 0ef0986: 8359168: Revert stdin.encoding usage in test/hotspot/jtreg/vmTestbase/nsk/jvmti/AttachOnDemand/attach010/attach010Agent00.java
• ... and 73 more: https://git.openjdk.org/jdk/compare/af87035b713f8bfe05a007a4d4670cefc6a6aaf2...master

Your commit was automatically rebased without conflicts.

[openjdk]

@kevinjwalls Pushed as commit 66535fe.

💡 You may see a message that your pull request was closed with unmerged commits. This can be safely ignored.

[kevinjwalls]

/backport :jdk25

[openjdk]

@kevinjwalls the backport was successfully created on the branch backport-kevinjwalls-66535fe2-jdk25 in my personal fork of openjdk/jdk. To create a pull request with this backport targeting openjdk/jdk:jdk25, just click the following link:

➡️ Create pull request

The title of the pull request is automatically filled in correctly and below you find a suggestion for the pull request body:

Hi all,

This pull request contains a backport of commit 66535fe2 from the openjdk/jdk repository.

The commit being backported was authored by Kevin Walls on 12 Jun 2025 and was reviewed by Alan Bateman and Serguei Spitsyn.

Thanks!

If you need to update the source branch of the pull then run the following commands in a local clone of your personal fork of openjdk/jdk:

$ git fetch https://github.com/openjdk-bots/jdk.git backport-kevinjwalls-66535fe2-jdk25:backport-kevinjwalls-66535fe2-jdk25
$ git checkout backport-kevinjwalls-66535fe2-jdk25
# make changes
$ git add paths/to/changed/files
$ git commit --message 'Describe additional changes made'
$ git push https://github.com/openjdk-bots/jdk.git backport-kevinjwalls-66535fe2-jdk25