[Jakarta HiveMind Wiki] Updated: HiveMindElementImprovementProposal

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

   Date: 2004-05-19T13:17:35
   Editor: HowardLewisShip <hl...@apache.org>
   Wiki: Jakarta HiveMind Wiki
   Page: HiveMindElementImprovementProposal
   URL: http://wiki.apache.org/jakarta-hivemind/HiveMindElementImprovementProposal

   no comment

Change Log:

------------------------------------------------------------------------------
@@ -17,12 +17,14 @@
 
 = Solution =
 
-Inlcude within the '''org.apache.hivemind.Element''' object a minimal number of utility methods that allow the developer who chooses to recieve raw elements instead of using one of !Hivemind's {{{<conversion>}}} or {{{<rules>}}} xml->obeject methods can do so more easily.
+Includewithin the {{{org.apache.hivemind.Element}}} object a minimal number of utility methods that allow the developer who chooses to recieve raw elements instead of using one of !HiveMind's {{{<conversion>}}} or {{{<rules>}}} xml->obeject methods can do so more easily.
 
 I would suggest minimaly a {{{String asXML()}}} method with returns a ''String'' representation of the Element.  Other methods could be included obvoulsy although care should be taken to respect the ["YAGNI"] principal.
 
 
 = Comments =
 
-Please add comments, ideas and suggestions..
+HowardLewisShip: It would not be impossible to create an adaptor that emulated W3C Dom, based on data obtained from !HiveMind's Element.
+
+In addition, if you have very sophisticated XML you want to parse, then put it in a seperate file and reference it as a {{{Resource}}}. You can then use the XML parser of your choice.
 

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