Hi Sander > I'm not really sure about that, all i know is that the > ConfigurationRegistry allowed me to stop thinking about Wicket's > serialization process :)
Yes, it was quite magic! > What about "active record" operations like record.refresh(), > record.store() etc, are those covered by the ExecuteListener too? My integration tests for those methods still run with the adapted implementation. Internally, "active records" run queries that send events to their registered ExecuteListeners, which can provide a JDBC Connection before execution. > If you explain to me how to do this kind of thing with the > ExecuteListener API, i could try it out and see if anything breaks in > my existing applications. That would be nice. I'll document this thoroughly when I'll release 2.1.0. There's no hurry, I'll keep the deprecated ConfigurationRegistry around for a while, as a fall-back. Thanks! Lukas
