Analyzer::Java::JaxRs
Inherits Analyzer < FileHelper < Reference < Object
Constants
Manifest basenames a derivative framework can only show up in.
Helidon MP's own quickstart is the concrete case: its JAX-RS
resource classes carry no io.helidon import at all — the
runtime is pulled in solely via pom.xml's
io.helidon.microprofile.* dependencies, so a .java-only scan
would never see the marker and JAX-RS would double-count those
routes under java_jaxrs too.
Frameworks that ride on JAX-RS but ship their own analyzer.
Listing them here keeps the JAX-RS analyzer the fallback for
vanilla Jersey / RESTEasy resources without double-counting.
io.helidon.microprofile routes to Analyzer::Java::HelidonMp,
which drives this same extractor under the java_helidon_mp tech.
jaxrs_or_websocket_source? gates the per-file tree-sitter parse;
one precompiled Regex.union scan (PCRE2 JIT, auto-escapes each
literal) replaces 5 separate String#includes? passes over the
same buffer.
Class methods
Instance methods
Instance-side view of the same declaration. The per-file rescues live on
this base class, which has no way to name the analyzer that is running
inside them, so a skipped file could not be attributed to a tech.
Deriving it from analyzer_for keeps the name written exactly once.