But by all means I didn't want to start another Hivemind vs. Spring flamewar
so please keep calm ;)
I haven't been on the list that long, so if there was one I missed it... ;-)
Anyway - no, I don't want to start that. I also don't want to suggest
that Spring is just plain better than HiveMind or even that HiveMind
should be replaced with Spring.
It's just that I started off with Spring, and decided to base my project
on it and am now hoping to avoid to have to do things twice - once in
the HiveMind/Tapestry layer and once in the Spring-based layers.
Validation is one very good example for this - both frameworks have a
validation logic, I need validation in both view (Tapestry) and service
layer (Spring) but I don't want to have to write the same logic two ways
- and have to fight forever to keep them in sync.
The other thing is - instead of adding new things from scratch, why not
use Spring, for example the way James says he has done for Transactions
and ORM (I haven't seen his code yet).
It will save the people who do the implementation a lot of time and it
will save the user from having to learn yet another different way of
doing something using a Hivemind add-on that he already has or knows how
to do in Spring.
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
