Hivemind makes it very easy to do what you describe. The easiest setup would be to create a 'platform' jar that contains the java model for your menus ect and the hivemodule.xml with the configuration points. Then each 'module' could go into a seperate jar and contribute to the configuration points specified in the platform. Note that this relies on the classpath to decide what is enabled at runtime which depending on how you want to deploy/distrobute could lead to more trouble than it is worth (ie you would need to test with all configurations of classpaths and even then if one client is experiencing a bug that another is not classpath related bugs can be very difficult to track down). My advice would be to always have all modules on the classpath and implement a license type framework that enables each module based on what they have purchased.
Good luck. On 11/23/05, Vinicius Carvalho <[EMAIL PROTECTED]> wrote: > Hello there! First I'm sorry about this question, I did not had the proper > time for a more in depth search on this subject. Anyway... > We're facing a problem with our software, we're creating modules for it. > The basic idea is: if you buy modules A & B, the menus, configuration > screens, change displaying new information. All the user needs to do is > deploy the new modules (some jars). We're searching jplugin for it, but I > found it too immature for production use. So I remember Hivemind (since I'm > a Tapestry user). > I was thinking if one could achieve such functionality with Hivemind. > Create a base system, and by having modules with new contributions, the > system would be customized per client? > > Regards and good coding > > Vinicius Carvalho > --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
