cocoon-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Paul Russell <p...@luminas.co.uk>
Subject Re: XObject
Date Fri, 01 Dec 2000 14:07:36 GMT
On Fri, Dec 01, 2000 at 02:37:17PM +0100, Sylvain Wallez wrote:
> Nice idea, but XObject is an interface. To change it to a proxy, you
> have to make it a class, thus inevitably breaking existing code. To
> avoid that while preparing the C1->C2 transition, I think it's better to
> have a new clean SAX2 compliant XObject (X2Object ?) and deprecate the
> old one. This will warn current C1 users that they should migrate to
> X2Object to be compatible with C2 while allowing them to keep their
> current code unchanged if they want to stay with C1.

Ack. Didn't realise it was an interface. How do classes get an
implementation of it? (sorry - I'm not familiar with the C1 code-
base).

> Also, the C2 <xsp:expr> tag does just a String.valueOf() of it's
> content, whereas C1 has full set of overloaded methods to handle many
> differing data types, including XObject. Why was it abandoned in C2 ?

I suspect it was more that Ricardo (It was you who wrote C2 XSP,
yes?) didn't get around to it yet...


P

-- 
Paul Russell                               <paul@luminas.co.uk>
Technical Director,                   http://www.luminas.co.uk
Luminas Ltd.

Mime
View raw message