I find spring easier to use. There's not much difference in what the two can do in terms of dependency injection. The one thing that makes hivemind different is the whole configuration point/ contribution idea which makes it easier for things to plug right in by simply dropping a properly configured jar. Other than that, the new spring 2.0 has all the features such as the scoping, lazy init, and all that. Apart from dependency injection, spring has a whole slew of other features that can be useful, such as Acegi for security, excellent AspectJ integration, Transaction management, and hibernate integration. You might consider using spring for these reasons.
On 11/21/06, Andrea Chiumenti <[EMAIL PROTECTED]> wrote:
Go well with hivemind, because it can do everything Spring does (and sometime even better). However a look @ Spring can enforce your skill ;-P kiuma On 11/21/06, Cyrille37 <[EMAIL PROTECTED]> wrote: > > Hello, > > I'm new with Tapestry. I've selected Tapestry for my future project > because of its simplicity and its wysiwyg capabilities. > I'd done well the tutorial, and have workbench example running well. > That's great ;-) > > By the way, here are some questions : > > Should I learn and use Spring with Tapestry or Hivemind is enough ? > Is Tapernate stable and ready for production ? If not, how to integrate > Hibernate ? > > Thanks a lot for your comments, > cyrille. > > --------------------------------------------------------------------- > To unsubscribe, e-mail: [EMAIL PROTECTED] > For additional commands, e-mail: [EMAIL PROTECTED] > >
--------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
