hivemind-commits mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From hivemind-...@jakarta.apache.org
Subject [Jakarta HiveMind Wiki] Updated: FeatureRequest
Date Fri, 02 Jul 2004 15:29:42 GMT
   Date: 2004-07-02T08:29:41
   Editor: NareshSikha <naresh.sikha@schwab.com>
   Wiki: Jakarta HiveMind Wiki
   Page: FeatureRequest
   URL: http://wiki.apache.org/jakarta-hivemind/FeatureRequest

   no comment

Change Log:

------------------------------------------------------------------------------
@@ -137,7 +137,7 @@
 
 In general, there is nothing really 'Hivemind' about Hivemind based Services. These Services
simply follow a regular pattern for wiring and invocation and express this in meta data. Taking
this one step further these Services could be developed and specified using some, external,
specification and Hivemind could merely be the container.
 
-It is in this spirit that I propose the following. All of these feature additions could be
implement alongside current features.
+It is in this spirit that I propose the following. All of these feature additions could be
implement alongside current features and have surfaced from attempting to introduce the Hivemind
system into a community industry standard pundits.
 
 == Publish module.xsd ==
 
@@ -146,3 +146,15 @@
 == Allow for META-INF/module.xml, META-INF/module.sdl ==
 
 The descriptor files found throughout the industry have a file name that is indicative of
the root element it contains. This seems natural and doesn't introduce the 'hive' semantic
into what would otherwise be a regular .jar file of classes and interfaces.
+
+== Allow for multiple entry points into the Registry ==
+
+A good litmus test of any architecture is its ability to be viewed from multiple angles.
Hivemind lives up to this test by exposing the Registry API and the <set-service/>/Java
Bean property methods of obtaining Services. Why not allow (and advocate) other means such
as JNDI? An interesting article on theserverside.com attests to JNDI's often overlooked capabilities
(http://www.theserverside.com/news/thread.tss?thread_id=26932). A quick example of how this
might look for Services would be:
+
+{{{
+Context c = new InitialContext();
+MyService ms = (MyService) c.lookup("service:" + MyService.class.getName());
+MyConfiguration mc = (MyConfiguration) c.lookup("configuration:" + MyConfiguration.class.getName());
+}}}
+
+

---------------------------------------------------------------------
To unsubscribe, e-mail: hivemind-cvs-unsubscribe@jakarta.apache.org
For additional commands, e-mail: hivemind-cvs-help@jakarta.apache.org


Mime
View raw message