 |
|
|
On Fri, Jan 2, 2009 at 12:57 AM, Dimitre Novatchev <dnovatchev@xxxxxxxxx> wrote:
> But this so called "XPath code" *is* in fact XSLT code.
That's the limitation of this tool.
In the current design, the XPath expression is treated as a string,
and I can only analyze the string using XPath (and probably XSLT)
built-in functions only.
--
Regards,
Mukul Gandhi
|
|
| |
These Archives are provided for informational purposes only and have been generated directly from the Altova mailing list archive system and are comprised of the lists set forth on www.altova.com/list/index.html. Therefore, Altova does not warrant or guarantee the accuracy, reliability, completeness, usefulness, non-infringement of intellectual property rights, or quality of any content on the Altova Mailing List Archive(s), regardless of who originates that content. You expressly understand and agree that you bear all risks associated with using or relying on that content. Altova will not be liable or responsible in any way for any content posted including, but not limited to, any errors or omissions in content, or for any losses or damage of any kind incurred as a result of the use of or reliance on any content. This disclaimer and limitation on liability is in addition to the disclaimers and limitations contained in the Website Terms of Use and elsewhere on the site.
| |
| |
|
|
|
