Hi Jurgen, Thanks for the feedback. I actually thought this was the least controversial change of the three :)
My thinking is that XML is about "mapping" between DB and Java, whereas callbacks are 100% about runtime object behavior unrelated to mapping. So it naturally belongs in Java and doesn't require an additional ORM abstraction (FWIW, I'd even get rid of annotations and let objects implement explicit callback interfaces for clarity and ease of processing). A similar earlier precedent was when we removed modeling of "listener" (non-entity) callbacks in XML in favor of doing it in the code. Andrus > On Jul 12, 2026, at 4:16 AM, Jurgen Doll <[email protected]> wrote: > > Hi Andrus > > With regards to (3) the "Removal of ObjEntity callbacks support from XML" I'm > not particularly in favour of this. > I like seeing in the model which ObjEntity have whatever callbacks allocated > to them. > It's like having one source of truth wrt the model, if it's removed then one > has to switch between XML model and implementation to see this information. > > Thanks, regards > Jurgen
