Mailing-List: contact axis-dev-help@ws.apache.org; run by ezmlm
Precedence: bulk
Reply-To: axis-dev@ws.apache.org
Received-SPF: pass (asf.osuosl.org: local policy)
Message-ID: <4309F967.3010906@sosnoski.com>
Date: Mon, 22 Aug 2005 09:12:23 -0700
From: Dennis Sosnoski <dms@sosnoski.com>
User-Agent: Mozilla Thunderbird 1.0.2 (X11/20050322)
MIME-Version: 1.0
To: axis-dev@ws.apache.org
Subject: Re: [Axis2] Databinding API issues
References: <43057D69.2050508@sosnoski.com> <430947EE.20108@gmail.com>
 <43096C13.7060805@sosnoski.com>
In-Reply-To: <43096C13.7060805@sosnoski.com>
Content-Type: text/plain; charset=ISO-8859-1; format=flowed
Content-Transfer-Encoding: 7bit

Dennis Sosnoski wrote:

> ...
> I understand the virtual nature of OM. I'd like to take advantage of 
> that when writing the actual serialized output, so that the OM stays 
> virtual when used for the output of a databinding operation. It looks 
> like this should be very easy to implement, though - I assume you're 
> using the OMNode.serialize() method for actually writing out the data, 
> right? Then it should be just a matter of implementing a custom 
> OMElement for each data binding framework, which knows how to 
> serialize out a saved data object to an XMLStreamWriter when the 
> serialize() method is called.

Actually, on thinking this over it shouldn't even require a custom 
OMElement for each data binding framework. Instead, it only requires a 
standard interface with a writeObject(XMLStreamWriter) method which each 
DataBindingSupporter class can implement. Then a single OMBindingElement 
subclass can be added to use this interface.

  - Dennis