On 10/22/01 5:45 AM, "Bojan Smojver" <[EMAIL PROTECTED]> wrote:
> "Geir Magnusson Jr." wrote: >> >> On 10/22/01 5:24 AM, "Bojan Smojver" <[EMAIL PROTECTED]> wrote: >> >>> "Geir Magnusson Jr." wrote: >>>> >>>> On 10/22/01 3:35 AM, "Jon Stevens" <[EMAIL PROTECTED]> wrote: >>>> >>>>> on 10/21/01 10:09 PM, "Daniel Rall" <[EMAIL PROTECTED]> wrote: >>>>> >>>>>> So the underlying JAXP implementation (Xerces), which is responsible >>>>>> for transforming the XML entity, is not doing its job. >>>>> >>>>> Anakia itself does ZERO parsing of any information. All it does is use >>>>> Xerces to parse the document and JDOM/XPath to traverse the tree. >>>> >>>> To be extremely precise, Anakia uses JDOM to parse, and no longer does >>>> Anakia suggest to JDOM which parser to use. Your original impl did specify >>>> Xerces to JDOM, but we ran into trouble with that. >>> >>> I think I read somewhere that XPath support in JDom is going to be >>> deprecated in favour of Jaxen. Is this something that's going to happen >>> to Anakia as well? >> >> Yep - I just looked at bob's Xpath site, and indeed, it's being deprecated >> in favor of Jaxen. >> >> Sounds good to me. Bob is your houshould name in high-quality Xpath >> products. (James too...) :) > > Since I always have a sinister agenda... > > Jaxen/Saxpath kind of abstract both Dom4J and JDom as well, so maybe > Anakia can be Jaxen based, rather them JDom based... Not that I'm > volunteering to write it ;-) > > Sorry for stirring to much... What does that give you? We have to go to Jaxen, it appears, but I think the anakia templates are tied to JDOM, right? -- Geir Magnusson Jr. [EMAIL PROTECTED] System and Software Consulting You're going to end up getting pissed at your software anyway, so you might as well not pay for it. Try Open Source.
