I've added interceptors into hibernate before with great success.
The method implementations pass in before / after data comparisons for you to look at / modify. It sounds like tricky stuff though(with how they normally document "all bets are off" type things when a rollback happens or exception occurs), make sure your unit tests cover everything :) On 5/23/06, James Carman <[EMAIL PROTECTED]> wrote:
All, I am trying to add some code into Tapernate which will "rollback" the POJOs that Hibernate has changed when a transaction is rolled back (the version or auto-generated id properties). I am going to attempt it using an interceptor. Has anyone every tried to do this before? I'm just wondering if there is a better approach. I'm actually changing Tapernate to include a "hibernate interceptor pipeline" so that you can contribute your own "interceptor filters" to do whatever you want. The "endpoint" of the pipeline will be an EmptyInterceptor, so if no interceptor filters are contributed to the pipeline, then nothing will happen. James --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
-- Jesse Kuhnert Tacos/Tapestry, team member/developer Open source based consulting work centered around dojo/tapestry/tacos/hivemind.
