[Jakarta HiveMind Wiki] Updated: NotXMLProposal

[hi...@jakarta.apache.org]

   Date: 2004-07-02T09:21:08
   Editor: NareshSikha <na...@schwab.com>
   Wiki: Jakarta HiveMind Wiki
   Page: NotXMLProposal
   URL: http://wiki.apache.org/jakarta-hivemind/NotXMLProposal

   no comment

Change Log:

------------------------------------------------------------------------------
@@ -324,3 +324,5 @@
 HowardLewisShip: I'm not saying that you '''can't''' build beans using the scripting language of your choice. I'm simply saying that doing so, you may lose some of the benefits of !HiveMind.  HiveDoc, for starters.  Line precise error reporting, potentially. And it adds to the dependencies. I'd certainly endorse the idea of an add-on library to let you use scripting if that's your way, but I don't want to see the core of !HiveMind screwed just to support scripting, which only ''some'' people think is the One True Path.
 
 SteveGibson: For us, we use a lot of XML already, so being able to keep XML for me is very important. A lot of people are saying they don't want to invent a new language - SDL. Well, to me, this looks a lot like IBMs Stanza format, used in AIX forever, and also the configuration format a company I used to work for came up with - purely because you specify the object you want to create and assign the properties. I think the SDL is very readable, and would probably use it if we didn't already use lots of XML files and *gasp* properties files.
+
+NareshSikha: I hope that the bulk of Hivemind Services and Configurations are written by junior developers who are more concerned about their resume than the strength of the architecture they are fulfilling. This will afford more time for architects and leads to solve the interesting problems. Therefore I think '''tools''' should be delivered to help devlopers author valid module definitions (Eclipse plugins are a good starting point). Then the details of the definition are more or less irrelevant. Barring that, please, please, give junior developers a chance to strength their industry standard skills in XML and what not by allowing for industry standard means for communicating metadata (XML).

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