Date: 2004-07-02T08:18:55 Editor: NareshSikha <[EMAIL PROTECTED]> Wiki: Jakarta HiveMind Wiki Page: FeatureRequest URL: http://wiki.apache.org/jakarta-hivemind/FeatureRequest
no comment Change Log: ------------------------------------------------------------------------------ @@ -132,3 +132,17 @@ }}} Alternatively, provide constant string values for all services exposed from the hivemind module so users don't have to read the SDL to figure out the service id. But this would be an onerous task and would need to be constantly synched with the SDL itself - hence the initial proposal of making the service id and service interface class name interchangeable for "default" usage. + += Separate Interface from Implementation = + +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. + +== Publish module.xsd == + +A published schema would allow unknown tools to be able help the developer author the requisite metadata. + +== 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. --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
