> For the complete documentation index, see [llms.txt](https://coldbox-orm.ortusbooks.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://coldbox-orm.ortusbooks.com/v1.x/coldbox-orm-event-handler/orm-to-coldbox-interceptions.md).

# ORM To ColdBox Interceptions

![](https://raw.githubusercontent.com/wiki/coldbox-modules/cbox-cborm/ORMEventHandlerBroadcast.jpg)

We have also expanded the hibernate ORM events to bridge the gap to the ColdBox interceptors. So now all the hibernate interceptors will relay their events to ColdBox via interceptors. This means that each hibernate event, like *preLoad()* for example, will announce its ColdBox counterpart: *ORMPreLoad()*. Below are the new interception points the ORM Event Handler exposes with the appropriate interception data it announces:

| Interception Point | Intercept Structure | Description                       |
| ------------------ | ------------------- | --------------------------------- |
| ORMPostNew         | {entity}            | Called via the postNew() event    |
| ORMPreLoad         | {entity}            | Called via the preLoad() event    |
| ORMPostLoad        | {entity}            | Called via the postLoad() event   |
| ORMPostDelete      | {entity}            | Called via the postDelete() event |
| ORMPreDelete       | {entity}            | Called via the preDelete() event  |
| ORMPreUpdate       | {entity,oldData}    | Called via the preUpdate() event  |
| ORMPostUpdate      | {entity}            | Called via the postUpdate() event |
| ORMPreInsert       | {entity}            | Called via the preInsert() event  |
| ORMPostInsert      | {entity}            | Called via the postInsert() event |

With the exposure of these interception points to your ColdBox application, you can easily create decoupled executable chains of events that respond to ORM events. This really expands the ORM interceptor capabilities to a more decoupled way of listening to ORM events. You can even create different interceptors for different ORM entity classes that respond to the same events, extend the entities with AOP, change entities at runtime, and more; how cool is that.


---

# Agent Instructions
This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com.

## Querying This Documentation
If you need additional information that is not directly available in this page, you can query the documentation dynamically by asking a question.

Perform an HTTP GET request on the current page URL with the `ask` query parameter, and the optional `goal` query parameter:

```
GET https://coldbox-orm.ortusbooks.com/v1.x/coldbox-orm-event-handler/orm-to-coldbox-interceptions.md?ask=<question>&goal=<endgoal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is optional and describes the broader end goal you are ultimately trying to accomplish on behalf of the user. GitBook uses it to tailor the answer towards what is most useful for that goal.

The response will contain a direct answer to the question and relevant excerpts and sources from the documentation.

Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.