[XML-DEV Mailing List Archive Home] [By Thread] [By Date] [Recent Entries] [Reply To This Message]

Re: RFC: Simple XML Event-Based API for Java

• From: Toby Speight <tms@a...>
• To: "XML developers' list" <xml-dev@i...>
• Date: 17 Dec 1997 10:48:20 +0000

Antony> Antony Blakey <URL:mailto:antony@n...>

> In article <34974325.6314AD85@n...>, Antony wrote:

Antony> [1  <multipart/mixed>]
Antony>
Antony> [1.1  <text/plain; iso-8859-1 (quoted-printable)>]
Antony> David Megginson wrote:
>> I would lose Ælfred's resolveEntity() callback

Antony> One of the major pains we have had using the available XML
Antony> tools is the lack of a resolveEntity() callback.  Originally
Antony> we wanted to use PUBLIC identifiers and resolve them using a
Antony> catalog, but now we use SYSTEM urls and have a dedicated http
Antony> host to resolve resources. Unfortunately we need to ship tools
Antony> to customers who may not be able to resolve the URL.  It is
Antony> not feasible to change the SYSTEM identifiers.  What we need
Antony> to do is change the URL on the fly (ie redirect through a
Antony> proxy or a lookup), or actually provide the input stream from
Antony> within the program ie. the entity is stored as a string, or
Antony> accessed through ClassLoader.getResourceAsStream().  This is
Antony> also neccessary if you want to store resources in a versioned
Antony> object base and have the version number implicit in the
Antony> processing, rather than explicitly mentioned in the URL
Antony> (although we have in fact done exactly this :)

ISTM that there's no difficulty in bolting on an XmlEntityResolver
interface to the design, and a method in XmlProcessor to register it
(just one small interface, David!).  An XmlApplication could implement
the resolver interface, so it doesn't necessarily imply a proliferation
of classes.

However, I say it should be kept as simple as possible (but no simpler)
to start with, and goodies like the resolver can be added once there
are some implementations.  Perhaps we'll want a "Level 2" API that
extends the interfaces in the Level 1 API?


[8-line sig snipped]

Antony> [1.2 Card for Antony Blakey <text/x-vcard; us-ascii (7bit)>]
Antony>
Antony> [2 S/MIME Cryptographic Signature <application/x-pkcs7-signature>]

I agree with PMR's comments on this lot (why can't people just include
an URL to their personal information, like my X-Author-Info header?)

--

xml-dev: A list for W3C XML Developers. To post, mailto:xml-dev@i...
Archived as: http://www.lists.ic.ac.uk/hypermail/xml-dev/
To (un)subscribe, mailto:majordomo@i... the following message;
(un)subscribe xml-dev
To subscribe to the digests, mailto:majordomo@i... the following message;
subscribe xml-dev-digest
List coordinator, Henry Rzepa (mailto:rzepa@i...)

• References:
  • RFC: Simple XML Event-Based API for Java
    • From: David Megginson <ak117@f...>
  • Re: RFC: Simple XML Event-Based API for Java
    • From: Antony Blakey <antony@n...>

• Prev by Date: inclusions/exclusions/named groups
• Next by Date: Re: RFC: Simple XML Event-Based API for Java
• Previous by thread: LISTRIVIA (Duplicate postings)
• Next by thread: Re: RFC: Simple XML Event-Based API for Java
• Index(es):
  • Date
  • Thread