axis-java-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Ajith Ranabahu <>
Subject Re: [Axis2][OM] representing XML Infoset
Date Wed, 15 Sep 2004 12:18:20 GMT
Hi Alek
Here are few quick thoughts about the interface. Sorry I did not get a
chance to look at this earlier

1. Methods to create new objects (ex elements) like DOM. Should we
have this functionality inside our OM as well?
2. Do we need a class for namespace? For instance the om element
interface has a prefix and a namespace name according
to the infoset spec. since we are doing a minimal implementation,
doing this with just a String for now seems to be ok.
3. Facilities to remove children and change them are indeed useful.
4. Providing Iterators (in place of any other data structure like a
List) and defering the parsing is cool :)
5. Should we provide two (or morel) ways to do the same thing? For
example setting the attribute can be done in several ways. Perhaps
this is just the ease of use but reducing such items will reduce the
complexity at least in the initial stage.

On Wed, 15 Sep 2004 03:43:26 -0500, Aleksander Slominski
<> wrote:
> hi,
> following very initial plan of actions described in
> i have checked into scratch what i have for the most complex XML Infoset
> Item i.e. eii (or in non-XML-Infoset-jargon: XML Element Information Item):
> i think that this should be helpful when building first OM prototype
> (other  interfaces are very small and simple and i will be checking them
> in later)
> we need more discussion on what OM API should look like: in particular
> support for streaming, what convenience methods are needed, how to
> select subset DOM API and how implement it so memory footprint and
> performance is good.
> thanks,
> alek
> --
> The best way to predict the future is to invent it - Alan Kay

Ajith Ranabahu

View raw message