[AXIS2][OM] character iis and OM API

[Aleksander Slominski <as...@cs.indiana.edu>]

i think that for SOAP infoset API we can gain lot of "lightweight-ness" by using String directly 
instead of Text node wrappers for XmlInfoset Character Information Items?

i think we do not need to retain [parent] property for character ii and as well it is not needed to 
retain Boolean flag "[element content whitespace] A boolean indicating whether the character is white 
space appearing within element content (see [XML], 2.10 "White Space Handling"). Note that validating 
XML processors are required to provide this information. If there is no declaration for the containing 
element, or there are multiple declarations, this property has no value for white space characters. If 
no declaration has been read, but the [all declarations processed] property of the document information 
item is false (so there may be an unread declaration), then the value of this property is unknown for 
white space characters. It is always false for characters that are not white space."
http://www.w3.org/TR/xml-infoset/#infoitem.character

when DOM API is required String nodes can easily be converted to Text nodes so there is no loss in 
functionality just less memory overhead *when* full DOM API is not needed for some parts of SOAP 
envelope but just XmlInfoset ...

still we can build OM with OMText instead of String that would have [element content whitespace] 
property using OM builder configured to do so.

thoughts?

thanks,

alek

-- 
The best way to predict the future is to invent it - Alan Kay