Package org.apache.camel
Interface MessageHistory
public interface MessageHistory
Represents the history of a Camel
Message
how it was routed by the Camel routing engine.-
Method Summary
Modifier and TypeMethodDescriptionlong
Gets the elapsed time in millis processing the node took (this is 0 until the node processing is done)default long
The elapsed time since created.A read-only copy of the message at the point of this history (if this has been enabled).getNode()
Gets the node at the point of this history.Gets the route id at the point of this history.long
getTime()
Gets the point in time the message history was createdboolean
Used specially during debugging where some EIP nodes are not accepted for debugging and are essentially skipped.void
Used for signalling that processing of the node is done.void
setAcceptDebugger
(boolean acceptDebugger) Used specially during debugging where some EIP nodes are not accepted for debugging and are essentially skipped.
-
Method Details
-
getRouteId
String getRouteId()Gets the route id at the point of this history. -
getNode
NamedNode getNode()Gets the node at the point of this history. -
getTime
long getTime()Gets the point in time the message history was created -
getElapsed
long getElapsed()Gets the elapsed time in millis processing the node took (this is 0 until the node processing is done) -
getElapsedSinceCreated
default long getElapsedSinceCreated()The elapsed time since created. -
nodeProcessingDone
void nodeProcessingDone()Used for signalling that processing of the node is done. -
getMessage
Message getMessage()A read-only copy of the message at the point of this history (if this has been enabled). -
setAcceptDebugger
void setAcceptDebugger(boolean acceptDebugger) Used specially during debugging where some EIP nodes are not accepted for debugging and are essentially skipped. This allows tooling to avoid dumping message history for nodes that did not take part in the debugger. -
isAcceptDebugger
boolean isAcceptDebugger()Used specially during debugging where some EIP nodes are not accepted for debugging and are essentially skipped. This allows tooling to avoid dumping message history for nodes that did not take part in the debugger.
-