Re: Re[2]: Moving XMLC to ObjectWeb's SF

Hi Jake,

On Monday 27 January 2003 19:14, Jacob Kjome wrote:
> Hello Richard,
>
> Barracuda includes some classes that were meant to, eventually, be
> moved to the XMLC package.  This hasn't really happened yet.  

Hmmm. Which packages, and what do they do?

> We access Xerces implementation packages for much the same reason as XMLC
> does; because it needs more access to the DOM than the interfaces
> provide.  Of course, there may be ways to workaround this.

One of these workarounds could be to use XMLC API rather than Xerces to access 
the document - I guess the information needed is much the same in both cases 
(extended structure and metadata). Of course, this would tie Barracuda to 
XMLC, but I think that's no worse than being tied to a specific Xerces 
implementation.

> The way we should move forward is to figure out what packages use
> Xerces implementation classes directly, then figure out which of those
> really *need* to access those package rather than the standard
> interfaces.  Whatever is left over should probably either be moved to
> XMLC, or we should figure out if there are already classes in XMLC
> that provide the needed functionality.
>
> Barracuda definitely shouldn't need direct access to XML or DOM
> implementation classes.

Agreed.

Best regards,

Richard

-- 
Richard Kunze 

[ t]ivano Software, Bahnhofstr. 18, 63263 Neu-Isenburg
Tel.: +49 6102 80 99 07 - 0, Fax.: +49 6102 80 99 07 - 1
http://www.tivano.de, kunze@xxxxxxxxx