hivemind-user mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "James Carman" <>
Subject RE: Announcement: The HiveTranse family grows again and changes name!
Date Wed, 11 May 2005 13:46:38 GMT
I think putting a link to the HiveMind Utilities project would be a
wonderful idea.  Although, I would recommend changing the URL first.  Can
you create a new SF project named hivemind-utils (actually hivemind-contrib
might be more suitable, as it follows the usual naming convention that other
projects use)?  Then, we can put a link from the main HM site that says,
"Check out the contributions the HiveMind community has made!" or something.

-----Original Message-----
From: Jean-Francois Poilpret [] 
Sent: Wednesday, May 11, 2005 9:40 AM
Subject: RE: Announcement: The HiveTranse family grows again and changes

Hello Hugo,

Thank you very much for your enthusiastic support to HiveMind Utilities

Regarding integrating these modules into HiveMind, it was from the beginning
of my involvement into HiveTranse (previous name of the HiveMind Utilities,
which essentially focused on HM-Hibernate integration) that for licensing
reasons, HiveTranse could not be integrated into HiveMind distribution. At
this time (I think it must be September or October last year), some long
discussion occurred to determine that any library that depends on Hibernate
(LGPL license) could not be hosted on the Apache site. This is also at that
time that Howard suggested that I create a project on SF or some other OSS
repository. That I did a few months later (the time to make the first
hivetranse contribution cleaner).

Now I believe that, in the list of all libraries that HiveMind Utilities
depend on globally, probably Hibernate must be the only one to have this
licensing problem. In HM Utilities, only one module explicitely depends on
Hibernate, this is hivetranse.hibernate (plus the example.hibernate module
of course). So it would still be possible to consider integration of a part
of HM Utilities into HM distribution. I am quite open on this point.

One more thing: some time ago (beginning January I believe), Howard had also
said it seemed to him a good idea to have some external repository of
general utility HM modules.

Maybe one simple way to integrate could be as simple as putting a link to
the HM Utilities SF project (or the project web home which is more
"personalized" than the generic SF web interface) from the HiveMind site. 


	Jean-Francois Poilpret, HiveMind Utilities team

-----Original Message-----
From: Hugo Palma [] 
Sent: Wednesday, May 11, 2005 4:28 PM
Subject: Re: Announcement: The HiveTranse family grows again and changes

First of all, congratulations on the great work you've donne with 
HiveMind Utilities. If it wasn't for these project i think i wouldn't 
have made the Spring to Hivemind migration i did.

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 ?



Jean-Francois Poilpret wrote:
> Dear HiveMind users,
> I am glad to announce (after a long silent period) the new release 
> 0.4.0
> HiveTranse on SourceForge.
> Now the project has changed name into "HiveMind Utilities" but the URL
> 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
> just limited to transaction management.
> It must be noted that this release is still working with HiveMind 1.0
> 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
> 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
> comment on these.
> In 1-2 weeks time, I hope I will release a pre-version of HiveBoard 
> (also
> SourceForge), a client/server shared whiteboard system based on 
> HiveMind (and HiveMind Utilities of course). This could be a good way 
> to get
> 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
> 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
> service that can create and cache any kind of objects, and inject 
> dependencies into them (can be seen as a hivemind.BuilderFactory for a
> 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
> 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
> - 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: 
> The HiveMind Utilities team

To unsubscribe, e-mail:
For additional commands, e-mail:

To unsubscribe, e-mail:
For additional commands, e-mail:

To unsubscribe, e-mail:
For additional commands, e-mail:

View raw message