public interface Breakpoint
Breakpoint
are used by the Debugger
API.
This allows you to register Breakpoint
s to the Debugger
and
have those breakpoints activated when their Condition
s match.
If any exceptions is thrown from the callback methods then the Debugger
will catch and
log those at WARN level and continue. This ensures Camel can continue to route the message without having
breakpoints causing issues.Modifier and Type | Interface and Description |
---|---|
static class |
Breakpoint.State
State of the breakpoint as either active or suspended.
|
Modifier and Type | Method and Description |
---|---|
void |
activate()
Activates this breakpoint
|
void |
afterProcess(Exchange exchange,
Processor processor,
NamedNode definition,
long timeTaken)
Callback invoked when the breakpoint was hit and the
Exchange has been processed (after). |
void |
beforeProcess(Exchange exchange,
Processor processor,
NamedNode definition)
Callback invoked when the breakpoint was hit and the
Exchange is about to be processed (before). |
Breakpoint.State |
getState()
Gets the state of this break
|
void |
onEvent(Exchange exchange,
CamelEvent.ExchangeEvent event,
NamedNode definition)
|
void |
suspend()
Suspend this breakpoint
|
Breakpoint.State getState()
void suspend()
void activate()
void beforeProcess(Exchange exchange, Processor processor, NamedNode definition)
Exchange
is about to be processed (before).void afterProcess(Exchange exchange, Processor processor, NamedNode definition, long timeTaken)
Exchange
has been processed (after).void onEvent(Exchange exchange, CamelEvent.ExchangeEvent event, NamedNode definition)
exchange
- the Exchange
event
- the event (instance of CamelEvent.ExchangeEvent
definition
- the NamedNode
definition of the last processor executed, may be null if not
possible to resolve from tracingCamelEvent.ExchangeEvent
Apache Camel