>> Is your AOP Framework availible for public use ? > > Nope. So your AOP framework is not an option here. Let's stick with Hibernate.
> we're actually having a little trouble seeing what > benefits it would give us, which is why we haven't > released it Probably none. What advantage would it give to you if it's closed? And then you say: > I would use my AOP framework as the base for both > object model and persistence Of course you would, but I think that Hibernate is better choice as it can also benefit Hibernate project, not some closed and hyped AOP framework. And your persistence layer... umm... was it persistent hashmap? Nothing against it, but most of us rdbms is the backend we rely on and are familiar with. ------------------------------------------------------- This sf.net email is sponsored by:ThinkGeek Welcome to geek heaven. http://thinkgeek.com/sf _______________________________________________ Opensymphony-webwork mailing list [EMAIL PROTECTED] https://lists.sourceforge.net/lists/listinfo/opensymphony-webwork
