Return-Path: Delivered-To: apmail-ws-axis-dev-archive@www.apache.org Received: (qmail 83262 invoked from network); 6 Oct 2004 14:55:20 -0000 Received: from hermes.apache.org (HELO mail.apache.org) (209.237.227.199) by minotaur-2.apache.org with SMTP; 6 Oct 2004 14:55:20 -0000 Received: (qmail 52778 invoked by uid 500); 6 Oct 2004 14:52:12 -0000 Delivered-To: apmail-ws-axis-dev-archive@ws.apache.org Received: (qmail 52668 invoked by uid 500); 6 Oct 2004 14:52:11 -0000 Mailing-List: contact axis-dev-help@ws.apache.org; run by ezmlm Precedence: bulk Reply-To: axis-dev@ws.apache.org list-help: list-unsubscribe: list-post: Delivered-To: mailing list axis-dev@ws.apache.org Received: (qmail 52587 invoked by uid 99); 6 Oct 2004 14:52:10 -0000 X-ASF-Spam-Status: No, hits=0.1 required=10.0 tests=DNS_FROM_RFC_ABUSE X-Spam-Check-By: apache.org Received-SPF: pass (hermes.apache.org: local policy) Received: from [129.79.246.27] (HELO whale.cs.indiana.edu) (129.79.246.27) by apache.org (qpsmtpd/0.28) with ESMTP; Wed, 06 Oct 2004 07:52:09 -0700 Received: from [127.0.0.1] (whale.cs.indiana.edu [129.79.246.27]) by whale.cs.indiana.edu (8.12.11/8.12.11/IUCS_2.62) with ESMTP id i96Eq44q025540; Wed, 6 Oct 2004 09:52:05 -0500 (EST) Message-ID: <41640690.8050006@cs.indiana.edu> Date: Wed, 06 Oct 2004 09:52:00 -0500 From: Aleksander Slominski User-Agent: Mozilla Thunderbird 0.8 (Windows/20040913) X-Accept-Language: en-us, en MIME-Version: 1.0 To: "'axis-dev@ws.apache.org'" Subject: [AXIS2][OM] character iis and OM API X-Enigmail-Version: 0.86.1.0 X-Enigmail-Supports: pgp-inline, pgp-mime Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit X-Virus-Checked: Checked X-Spam-Rating: minotaur-2.apache.org 1.6.2 0/1000/N 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