The hivemind-hibernate3 library uses Spring and HiveMind together, but it uses Spring's Hibernate support in a HiveMind way. The pieces of Spring that you use for writing DAOs (or repositories as I've started calling them) don't really have anything to do with an IoC container. They're not hard-wired to only live inside the Spring container. So, I decided to not try to reinvent the wheel. I just wanted to put someone else's really nice wheels on my small, but very configurable vehicle. :)
On 11/4/07, Johan Maasing <[EMAIL PROTECTED]> wrote: > On 11/4/07, James Adams <[EMAIL PROTECTED]> wrote: > > > > Thanks Jean-Francois for your quick response. > > > > Yes I saw HiveTranse but it looks to be meager compared to what you get from > > Spring -- no offense intended, I'm just spoiled by the feature set and first > > class documentation of the Spring Framework plus the many articles, blog > > posts, etc. available from third parties about how to use Spring/Hibernate. > > No argument there, Spring has very good documentation. > > > like the IoC/wiring approach offered by HiveMind, but I've always used > > Hibernate in conjunction with Spring and it looks like with HiveMind I will > > have to either use vanilla Hibernate (maybe that's not as bad as I'm > > thinking and I should learn to live without the Spring crutches) or go with > > We all have different preferences but for me I do not find that Spring > actually offers much above vanilla Hibernate. You could also use > Spring & Hivemind (yes seems redundant) but it is very easy to use > spring beans from hivemind. > So I would say that it is worth your while to investigate those > options since HiveMind - to my mind - is a far superior IoC-container > to Spring since I could not live without the > configuration/contribution-feature in hivemind. >
