David Crossley wrote:
Antonio Gallardo wrote:
Hi forresters!
Seems like my "crazy" idea got accepted. ;-)
http://issues.apache.org/bugzilla/show_bug.cgi?id=32360#c10
Do you think this is going to help us to fix this error? :-)
I don't profess to understand the issues involved.
The final solution sounds like it will enable us to
make a useful workaround ... an API to define non-standard
things, e.g. context.setDefaultNamespaceIgnored(true)
It is non-standard for XPath 1.0, but it is standard for XPath 2.0.
Hence, we need a XPath 2.0 feature in a XPath 1.0 implementation. ;-)
BTW, Maybe we may suggest a new name for the method. :-)
Best Regards,
Antonio Gallardo.
In XPath 2.0 this is like:
Interesting. That is similar to the workaround that i am
currently trying to do, except from the Forrest end of things
before Cocoon input modules and JXPath read our site.xml file.
Thanks for your contributions.
Thanks to you.
-David
