hivemind-commits mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
Subject [Jakarta HiveMind Wiki] Updated: ConditionalContributionsProposal
Date Thu, 29 Apr 2004 19:26:54 GMT
   Date: 2004-04-29T12:26:54
   Editor: DanielFeist <>
   Wiki: Jakarta HiveMind Wiki
   Page: ConditionalContributionsProposal

   no comment

Change Log:

@@ -99,3 +99,7 @@
 LukeBlanshard, 17 April 2004:
 I was thinking more like '"${interface.module.!ServiceName}" == "implementation.module.!ImplementationName"'.
 Then you just arrange your symbol sources to look in standard places for these definitions,
and you have maximum configurability.
+DanielFeist 29 April 2004:
+My use case for conditional contributions is as follows:  A project implementation is made
up of reusable self-contained components and an amount of custom implementation.  Each component
is a !HiveMind module as if the custom implementation.  Each component defines its services
with service points in its own hivemodule.xml (inside their jar's) along with the default
implementations for these services.  This allows for each component to be autonomous and be
usable on it's on if nessecary.  When i use components for a specific implementation it maybe
the case that i don't want to use a default service implementation defined by a component
in it's hivemodule.xml but rather overwrite it and use another implementation.  I'm not sure
how this fits into the general proposal but I see it as a very common use case.  Maybe its
possible to have one hivemodule that has the last say about implementations?  Else how can
this use case be satisfied with !HiveMind without having to open up the component jar and
change it's hivemodule.xml?

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

View raw message