: : DOMUtils.getAttributeWithInheritance instead. My one scenario I came
: : across where I wanted some context passed down was "fieldName" and this
: : is handled simply by leaf nodes walking up the w3c.dom.Node tree until
: : you find an Element with this attribute set.
:
: Hmm, i can see how th
: But doesn't sticking with w3c.dom.Element allow the possibility of
: standards based tools (eg XPath implementations) to be used by builders
: if they so wish?
Hmmm... that isn't something i'd considered. You've convinced me.
: >3) I'm still confused about how state information could/would be
Hi Chris,
Thanks for taking the time to look at this in detail.
1) The factory classes should have "removeBuilder" methods so people
subclassing parsers can flat out remove support for a particular
tag, not just replace it.
Can do.
2) This DOM version definitely seems easier to follow
: Further to our discussions some time ago I've had some time to put
: together an XML-based query parser with support for many "advanced"
: query types not supported in the current Query parser.
:
: More details and code here: http://www.inperspective.com/lucene/LXQuery2.htm
So I *finally* got a
markharw00d wrote:
Further to our discussions some time ago I've had some time to put
together an XML-based query parser with support for many "advanced"
query types not supported in the current Query parser.
More details and code here:
http://www.inperspective.com/lucene/LXQuery2.htm
Mark,
