It depends entirely on the context of the app. Tap has some dependancies on hivemind, so you will wind up dealing with hivemind and hivemind configs to some extent no matter which solution you use. However, the spring integration is very easy to use, and it is easily possible to keep all of the layers and support classes that aren't web/tapestry specific in your spring config and use them from within tapestry as easily as you can use objects managed by Hivemind. Fundamentally, Spring makes working with Hibernate based entities an absolute breeze, and that isn't something to be disregarded. And AOP via AspectJ really simplifies some other things, such as changelogs and transaction management (spring will happily manage all your transactions for you via AOP, if you ask it to). If you will be using hibernate for entity storage and/or want acegi or AOP, then the choice is made for you. Use Spring. If not, hivemind is the solution that is native to tapestry, so you might as well use that. Another issue to consider is that Spring is probably more likely to crop up on other projects you may build in the future, so it may be useful to you, personally, to use it.
--sam --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
