By default, the Java Agent makes a best-effort basis to name JAX-RS-based transactions using the class annotation, method annotation, and HTTP method of the detected entry point, in the following form:

{class-annotation}/{method-annotation}.{http-method}

In some situations where the annotation values are not available, the agent may name the transaction as follows:

{fully qualified class name}.{method}

For example, when the JAX RS service endpoints don't have the class and method names in them explicitly, but the annotations are inferred in some other way.

For annotation inheritance cases, the agent attempts to fetch the annotations from the superclasses and interfaces as described by the JAX RS specification. The specification makes the following recommendation:

“For consistency with other Java EE specifications, it is recommended to always repeat annotations instead of relying on annotation inheritance.”

Repeating annotations on the endpoint methods enables the Java Agent to name business transaction according to the default scheme.