XOM API for Processing XML with Java

[Nils_Kilden-Pedersen AT Countrywide.Com]

xom-interest-bounces AT lists.ibiblio.org wrote on 11/10/2003 05:34:25 PM:

> At 2:25 PM +0000 11/10/03, Janek Bogucki wrote:
> 
> >Then you get this heirarchy:
> >
> >Serializer
> >   |
> >   + ConfigurableSerializer
> >   |
> >   + CanonicalXMLSerializer
> >
> >This is an improvement as the inappropriate setter methods do not 
> >exist on CanonicalXMLSerializer
> >and any method expecting a Serializer will not be surprised by 
> >IllegalArgumentExceptions.
> 
> That makes some sense, but it's not like the methods in Serializer 
> don't belong there; and I don't like adding excess classes to the 
> core API. I think a lot of developers would end up either complaining 
> about not having enough options in Serializer (if they don't notice 
> ConfigurableSerializer) or complaining about having to always type 
> "Configurable". I think prefer just the one Serializer class.

Nonetheless, in an OO perspective that's what you should do. Maybe you'll 
like this better:

AbstractSerializer
   |
   + Serializer
   |
   + CanonicalXMLSerializer



Nils
>From ckr AT ti.com  Wed Nov 12 11:48:29 2003
Return-Path: <ckr AT ti.com>
Delivered-To: xom-interest AT lists.ibiblio.org
Received: from go4.ext.ti.com (go4.ext.ti.com [192.91.75.132])
        by happyhouse.metalab.unc.edu (Postfix) with ESMTP id D64BD20097
        for <xom-interest AT lists.ibiblio.org>;
        Wed, 12 Nov 2003 11:48:27 -0500 (EST)
Received: from dlep52.itg.ti.com ([157.170.134.103])
        by go4.ext.ti.com (8.12.10/8.12.10) with ESMTP id hACGmQTT006213
        for <xom-interest AT lists.ibiblio.org>;
        Wed, 12 Nov 2003 10:48:26 -0600 (CST)
Received: from dlep90.itg.ti.com (localhost [127.0.0.1])
        by dlep52.itg.ti.com (8.12.10/8.12.10) with ESMTP id hACGmQAK022865
        for <xom-interest AT lists.ibiblio.org>;
        Wed, 12 Nov 2003 10:48:26 -0600 (CST)
Received: from dfre01.itg.ti.com (dfre01.itg.ti.com [137.167.210.28])
        by dlep90.itg.ti.com (8.12.10/8.12.10) with ESMTP id hACGmPGv025231
        for <xom-interest AT lists.ibiblio.org>;
        Wed, 12 Nov 2003 10:48:25 -0600 (CST)
Received: by dfre01.itg.ti.com with Internet Mail Service (5.5.2653.19)
        id <S0VJBLP2>; Wed, 12 Nov 2003 17:48:10 +0100
Message-ID: <23FC7B6A090ED311A7F70000F8CB3A5B0DF37089 AT dfre02.itg.ti.com>
From: "Krueger, Carsten" <ckr AT ti.com>
To: "'xom-interest AT lists.ibiblio.org'" <xom-interest AT lists.ibiblio.org>
Date: Wed, 12 Nov 2003 17:48:06 +0100
MIME-Version: 1.0
X-Mailer: Internet Mail Service (5.5.2653.19)
Content-Type: text/plain;
        charset="iso-8859-1"
X-Mailman-Approved-At: Wed, 12 Nov 2003 12:35:12 -0500
Subject: [XOM-interest] XOM API stability
X-BeenThere: xom-interest AT lists.ibiblio.org
X-Mailman-Version: 2.1.2
Precedence: list
List-Id: <xom-interest.lists.ibiblio.org>
List-Unsubscribe: <http://lists.ibiblio.org/mailman/listinfo/xom-interest>,
        <mailto:xom-interest-request AT lists.ibiblio.org?subject=unsubscribe>
List-Archive: <https://lists.ibiblio.org/sympa/arc/xom-interest>
List-Post: <mailto:xom-interest AT lists.ibiblio.org>
List-Help: <mailto:sympa AT lists.ibiblio.org?subject=HELP>
List-Subscribe: <http://lists.ibiblio.org/mailman/listinfo/xom-interest>,
        <mailto:xom-interest-request AT lists.ibiblio.org?subject=subscribe>
X-List-Received-Date: Wed, 12 Nov 2003 16:48:29 -0000

Hi,

I wonder how stable the XOM API is. Are there any predictable changes
in the next versions ?

We are currently using JAXB 1.0 (Early Access) which seemed to do what
we want a while ago. It's only now that we had to discover that it is
buggy and even worse it's successor has a completely different design
and API - which would force us to completely rewrite our code.

XOM seems very promissing. Before trying to port our code to it I want
to insure as much as possible that we are not running into the same
problem again.

Thanks for your help.

Carsten