Spring may provide all of the things on my list of wishes already... I don't know as I only tried to use it for several days and changed to Hivemind as it's the tool Tapestry is build upon/uses and I don't need most of Spring's stuff (at least not at the moment).
That's why I wrote that I dream of having something similar for _Hivemind_: Because Tapestry is based on Hivemind and I don't want to be forced to use Spring if I don't need all the other stuff. To come back to my original statement: Perhaps we could adapt the code from Spring which handles sessions/transactions/persistent objects and include it into Hivemind? I don't know the internals of Hivetranse - perhaps this is already a project which takes this way? Perhaps if we can agree on HiveTranse as a possible basis for further development (actually I have to say that I have _nearly_ no problems concerning sessions/transactions using HiveTranse) There was another thread on this list some days ago - what should be changed/included into HiveTranse, the OpenSessionInView pattern for example, a data squeezer, what else? But by all means I didn't want to start another Hivemind vs. Spring flamewar so please keep calm ;) Cheers, Andreas --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
