I just had a rather tiresome day tracking down why xtag taglib stopped working when I upgraded my application to Dom4J release 1.3. It turns out that somewhere along the line, I believe between 1.1 and 1.2 dom4j changed the semantics on NodeFilter.matches() rather drastically. Since the xtag:if and xtag;when tags used the NodeFilter to do the unerlying test, it simply stopped working properly. I am attaching copies of the files that I had to change to fix this, so hopefully other poor souls who run into this can do something more enlightening with their Sunday ;-)
I used jakarta-taglibs-src-20020804.tar.gz as the code base for the changes.
I would love to see this rolled back into taglib, but I realize that is a hard call as a lot of old installations will sure to break. As usual this type of public interface changes creates a problem to be managed regardless of which way you play it. Perhaps a note in the docs would be useful.
I do not monitor any of these lists, so please email me directly at [EMAIL PROTECTED] if you have any questions.
Ciao,
Joel
taglib-fix.tgz
Description: application/compressed
