I gave some more thinking to Anakia redesigning yesterday, and I thought
it's just not elegant the way I originally made it. I SHOULD be able to
preserve backward compatibility. Finally, I figured out how could I
incorporate the new functionality WITHOUT losing backward compatibility.
Basically, I'll subclass the org.jdom.Element to have applyXPath() and
toString() implemented to behave identically to a single-element NodeList,
and make a custom JDOMFactory for it, then plug that factory into the
SAXBuilder used by Anakia. I'll also tweak TreeWalker and XPathTool to
return NodeList (it implements java.util.List as well, so it's backward
compatible).
This way, the new functionality becomes a feature of Element and everything
is backward compatible. There is no need for two different Anakias! Be back
soon after I'm done.
Attila.
----- Original Message -----
From: "Jon Stevens" <[EMAIL PROTECTED]>
To: "velocity-dev" <[EMAIL PROTECTED]>
Sent: 2001. augusztus 1. 17:09
Subject: Re: Creative criticism on Anakia design
> on 8/1/01 7:58 AM, "Szegedi Attila" <[EMAIL PROTECTED]> wrote:
>
> > However, I don't want to burden the mailing list with a 28 kbytes
> > attachment. Should I send the files to you, Jon?
> >
> > Cheers,
> >
> > Attila.
>
> Sounds good. The only thing that I'm not "happy" about is that it is
> Anakia2Task.java. I would rather it just be AnakiaNodeListTask.java
>
> Thanks!
>
> -jon
>
>
