All Classes and Interfaces
Class
Description
Registry for managing Qute template breakpoints during a debugging session.
Context for collecting code completions in the debugger.
Provides support for code completions within the Qute template debugger.
Utility class to parse conditional expressions into Qute TemplateNodes.
The
DebuggeeAgent manages the debugging process for Qute templates.Qute debugger API.
Implementation of
EvalContext used by the Qute debugger.Base exception class for all Qute debugger-related errors.
Listener interface for receiving debugger events from the Qute debugger.
Represents the possible states of the Qute debugger during a debugging session.
A
TraceListener implementation that connects the Qute engine's trace
events to the DebuggeeAgent.Debug Adapter Protocol (DAP) server implementation for Qute debugging.
Default implementation of
ValueResolverCollector that collects
properties and methods supported by a ValueResolver.Provides support for evaluating expressions in the context of a debugged template.
JavaSourceResolver implementation for event-based clients (VS Code, etc.).
A
RemoteSource representing a Qute template stored as a local file.Represents the global scope in the Qute debugger.
A specialized
RemoteSource representing a Qute template located
inside a JAR file.Arguments describing a Java element referenced from a Qute template.
Payload sent by the server to event-based clients (VS Code, etc.) when
requesting the resolution of a Java source corresponding to a Qute template.
Event response for a Java source location resolution.
Response containing the location of a Java method, class, or template content
referenced from a Qute template.
Resolver for Java source locations referenced from Qute templates.
Represents the local scope in the Qute debugger.
Represents the namespace resolvers scope in the Qute debugger.
Combined Debug Protocol client interface for Qute templates.
Reflection-based collector for value resolvers.
Represents a remote breakpoint set by the client through the Debug Adapter Protocol (DAP).
Represents a scope in the Qute debugger (e.g., locals, globals, namespace resolvers).
Represents a remote Qute template source used in the debug agent.
Represents a single Qute stack frame in the debugging process.
Represents a Qute debug thread that manages the execution flow of templates during debugging.
A remote variable in the debugger, which may have child variables.
Represents a group of
RemoteStackFrames belonging to a Qute section
(e.g.Registry responsible for managing
SourceResponse objects used by the
Debug Adapter Protocol (DAP) to serve source content for Qute templates.Registry responsible for resolving and managing mappings between Qute
template IDs and their corresponding
RemoteSource instances.Represents a "stopped" event in the Qute debugger.
Represents the possible reasons why the debuggee execution stopped.
Represents a thread event in the Qute debugger.
Represents the possible statuses of a thread during its lifecycle in the debugger.
Interface to collect information from a
ValueResolver for debugging
purposes.Context used by the debugger to collect properties and methods of an object
in a given stack frame.
Registry for Qute
ValueResolvers to support debugging completions
and variable inspection.Context for collecting variables in the debugger.
Helper utility for creating and managing debug variables.
Represents an entity that can provide a collection of debug variables
(properties, fields, or items) for inspection in the debugger.
Maintains a registry of all variables and variable containers
(implementing
VariablesProvider) in the debug session.