In Apache commons-jxpath we discuss a simpler way to relax the XPath 1.0
handling for default namespaces:
That isn't a relaxation it is just non conformant behaviour.
The proposed feature is broken (and the claim during the thread that
XSLT 1 processors work that way is incorrect).
XSLT2 does have a feature that allows a different interpretation of
unprefixed names in xpaths, but even there they do not match the default
namespace of the source file (which is just totally against the way
Xpath namespace bindings work)
I will be glad if you can comment about the issue and how do you see
this.
please don't do that or if its done, undo it!
David
________________________________________________________________________
This e-mail has been scanned for all viruses by Star. The
service is powered by MessageLabs. For more information on a proactive
anti-virus service working around the clock, around the globe, visit:
http://www.star.net.uk
________________________________________________________________________
--~------------------------------------------------------------------
XSL-List info and archive: http://www.mulberrytech.com/xsl/xsl-list
To unsubscribe, go to: http://lists.mulberrytech.com/xsl-list/
or e-mail: <mailto:xsl-list-unsubscribe(_at_)lists(_dot_)mulberrytech(_dot_)com>
--~--