Having said this, i just couldn't help thinking while i found the classes in this module more and more useful that they should be part of hivemind itself, and not a separate project. I think this would great both for hivemind and utilities. Utilities would have more visibility, therefore more support from the community and hivemind itself would be a more complete and easy to use framework out-of-the-box.
What are your thoughts about this ?
Cheers
Hugo
Jean-Francois Poilpret wrote:
Dear HiveMind users,
I am glad to announce (after a long silent period) the new release 0.4.0 of HiveTranse on SourceForge.
Now the project has changed name into "HiveMind Utilities" but the URL have not changed however. This name change is due to the fact that the project now hosts a bunch of various utilities dedicated to applications built with HiveMind, and is not just limited to transaction management.
It must be noted that this release is still working with HiveMind 1.0 only. It will probably be the last release to work with HM1.0, the next release should be a port to HM1.1 (but lately I did not have much time to play with the latest HM1.1 beta however...)
The original SourceForge announcement is at the end of this mail.
Please do not hesitate to give a try to the various modules provided and to comment on these.
In 1-2 weeks time, I hope I will release a pre-version of HiveBoard (also on SourceForge), a client/server shared whiteboard system based on HiveMind (and HiveMind Utilities of course). This could be a good way to get quickly started with the possibilities of HiveMind Utilities modules.
Cheers
Jean-Francois Poilpret
Announcement on SourceForge: The HiveTranse family grows again and changes name!
At the occasion of 0.4.0 release, the HiveTranse project team is glad to announce several modifications into the project.
First, due to its wider scope, the HiveTranse project is now renamed "HiveMind Utilities", however the name code on SourceForge still remains "hivetranse".
In release 0.4.0, the HiveMind Utilities project has had the following modifications: - refactoring of hivetranse.utils module into hiveutils module and renaming of packages in this module (net.sourceforge.hivetranse) to net.sourceforge.hiveutils. - removal of web.utils module, which content has been moved to hiveutils module. - new features added to hiveutils module, in particular a new ObjectBuilder service that can create and cache any kind of objects, and inject dependencies into them (can be seen as a hivemind.BuilderFactory for a wide range of objects (each such object is defined in a configuration point in order to ease usage of this feature). - renaming of hivetranse.transaction module to hivetranse.core. No package has been renamed however. - creation of new hiveevents module. - creation of new hivegui module.
To summarize, HiveMind Utilities project, as of release 0.4.0, contains the following modules: - hiveutils: set of useful classes and services for HiveMind-based applications - hivetranse.core: advanced generic transaction management framework - hivetranse.jdbc: support for JDBC persistence layer in your DAOs - hivetranse.hibernate: support for Hibernate persistence layer in your DAOs - hivetranse.ibatis: support for iBATIS SqlMaps persistence layer in your DAOs - hivelock.core, hivelock.shared, hivelock.default: support for security management (authentication, authorization, stateful services) - hiveremoting.caucho: "Web Services" support for your HiveMind services, through Caucho's hessian and burlap protocols (over http). - hiveevents: event notification service
For more information on HiveMind Utilities project: http://sourceforge.net/projects/hivetranse/
The HiveMind Utilities team
--------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
