Rod (Johnson) has repeatedly suggest that we leverage their implementation of transactions. I've been short on time pursuing that. I think I would whip together a simple transaction interceptor in a few hours, and probalby not much longer to try and grok the Spring Transaction support and turn that into an interceptor.
The overlap doesn't bother me too much and it's certainly a great way to leapfrog functionality in HiveMind, by leveraging what Spring already offers. Rod is interested in the other way, since Spring doesn't have anything sufficiently like configurations. You don't have to zoom in very far to see that HiveMind and Spring are significantly different from each other and, I think , complementary. ----- Original Message ----- From: Drew McAuliffe <[EMAIL PROTECTED]> Date: Thu, 1 Jul 2004 12:29:55 -0700 Subject: Spring-like transaction features? To: [email protected] Are there any plans to introduce features into HiveMind like Spring's abstraction of transactionality of Hibernate or other data access? I like the way that Spring can make the details of data access and transactionality configurable but I prefer the way HiveMind deals with the overall service abstraction, pluggability, interception, etc. Is there any plan to introduce these higher-order features into HiveMind, or is it still concentrating mainly on the IoC/container/pluggability side of things? Or does anyone out there have a HiveMind module that does a similar thing? I'm investigating moving a combination of homegrown app layers to either one of these two big guys, and I don't like the idea of mixing them because of the functionality overlap. Thanks, Drew -- Howard M. Lewis Ship Independent J2EE / Open-Source Java Consultant Creator, Jakarta Tapestry Creator, Jakarta HiveMind http://howardlewisship.com --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
