Skip to content

Document resolvers in the Javadoc overview - #81

Merged
garydgregory merged 2 commits into
apache:mainfrom
ppkarwasz:docs/resolvers
Sep 1, 2026
Merged

Document resolvers in the Javadoc overview#81
garydgregory merged 2 commits into
apache:mainfrom
ppkarwasz:docs/resolvers

Conversation

@ppkarwasz

Copy link
Copy Markdown
Member

A secured factory inverts what a resolver means: returning null leaves the reference unresolved and the floor answers it with empty content, rather than handing the reference back to the parser to fetch. A resolver is therefore the only way to opt a resource back in, which the overview did not say anywhere.

Adds a Resolvers section to overview.html:

  • what a null return now means, and that a non-null result is honored even where the JAXP 1.5 external-access properties would deny the fetch;
  • which identifier to match against an allow-list, absolute for EntityResolver and relative plus a base URI for the others;
  • one worked example per resolver API (EntityResolver, LSResourceResolver, URIResolver, XMLResolver), each naming the channels that resolver covers;
  • links to the Java 25 API documentation at the first mention of each JAXP, SAX and DOM type.

Documentation only, no main code changes.

🤖 Generated with Claude Code

A secured factory inverts what a resolver means: returning null leaves the
reference unresolved and the floor answers it with empty content, instead
of handing the reference back to the parser to fetch. A resolver is
therefore the only way to allow a fetch, and the identifier to match
against an allow-list differs per API, absolute for EntityResolver and
relative plus a base URI everywhere else.

Add a Resolvers section to the Javadoc overview with one worked example per
resolver API, name the channels each one covers, and link the JAXP, SAX and
DOM types to the Java 25 API documentation at their first mention.

Assisted-By: Claude Opus 5 (1M context) <noreply@anthropic.com>
Claude-Session: https://claude.ai/code/session_01XVaEa2R2sHtBgJh8Mhv841
The JDK 11 javadoc HTML checker reads the bare ">" of "->" as stray markup
and fails the build with "bad use of '>'"; the JDK 17 and later checkers
accept it, so the samples passed locally. Write the arrow as "-&gt;", which
renders identically.

Assisted-By: Claude Opus 5 (1M context) <noreply@anthropic.com>
Claude-Session: https://claude.ai/code/session_01XVaEa2R2sHtBgJh8Mhv841

@garydgregory garydgregory left a comment

Copy link
Copy Markdown
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

LGTM.

@garydgregory
garydgregory merged commit 6c2b441 into apache:main Sep 1, 2026
17 checks passed
@ppkarwasz
ppkarwasz deleted the docs/resolvers branch September 1, 2026 19:25
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants