Sanjiva,
I think you will find that your assertion at bottom
on namespaces is slightly misleading.
We've been grappling with this exact same issue over in the
CAM TC. Here's what happens - if the XML content has a
default namespace declaration in it - then the XPath parser
will demand prefixes, even if you don't use them!
This is an ugly bug and side-effect.
The only recourse we have is to just warn people - do
not use namespace declarations - unless you absolutely
need them.
There are very few instances where you really need
namespaces in XML streams - paradoxically one is
CAM templates - since they have embedded markup
instructions to the CAM processor - and of course
these need to be discarded from the overall content
processing.
Namespaces and their side-effects are something
that XML is going to have to live with for a longwhile
downstream.
Fortunately tools like CAM remove the need to use
namespaces in business transaction documents -
therefore making their processing consistent and
reliable. Simple plain-vanilla XML is my preference
everytime.
DW.
=================================================
Message text written by "Sanjiva Weerawarana"
>
XPath 1.0 does not require qualification unless the element/attribute
itself is qualified. How else could it work??
What's the validation for unqualified stuff? I don't know of any myself.
<
