Hi Bill,
Thanks for replying. Yes, most of the work I've seen with Hibernate & AOP is with transaction interceptors & safely ignores mixin persistence. As I mentioned before, I covered my first investigation into this on the forum [http://forum.hibernate.org/viewtopic.php?t=931018], but I will be working on tighter integration with Hibernate in the near future. Any comments regarding my approach or conclusions are still welcome.
If people are interested in this area then I'm more than happy to post my work for discussion, I just don't want to cover ground that is currently being worked on.
Mark
From: Bill Burke <[EMAIL PROTECTED]>
We haven't really thought about it much yet. JBoss AOP has focused mostly these areas so far:
1. The framework itself 2. These aspects: asynchronous, tx, security 3. A little bit on remoting
We haven't done much with persistence yet. If you have anything you'd like to research or discuss, ideas and/or code is definately welcome.
Gavin and Christian don't like field interception much, but I'd like to see where it could take us in persistence land. It is quite easy to take advantage of it with a framework like JBoss AOP. Or Caching stuff is already doing it with some success. As far as introductions and mixins and such goes, we'll have to figure out something in the future. Again, help is greatly appreciated.
_________________________________________________________________ Express yourself with cool new emoticons http://www.msn.co.uk/specials/myemo
------------------------------------------------------- This SF.Net email is sponsored by the new InstallShield X.
From Windows to Linux, servers to mobile, InstallShield X is the one
installation-authoring solution that does it all. Learn more and evaluate today! http://www.installshield.com/Dev2Dev/0504 _______________________________________________ hibernate-devel mailing list [EMAIL PROTECTED] https://lists.sourceforge.net/lists/listinfo/hibernate-devel
