Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Upgrading Firepath to use XPATH 2.0 version #42

Open
GoogleCodeExporter opened this issue Jul 26, 2015 · 2 comments
Open

Upgrading Firepath to use XPATH 2.0 version #42

GoogleCodeExporter opened this issue Jul 26, 2015 · 2 comments

Comments

@GoogleCodeExporter
Copy link

What steps will reproduce the problem?
1. Using any functions that is under XPATH version 2.0 like ends-with, if.. 
else, for

E.g., //text()[ends-with(.,':')]

What is the expected output? What do you see instead?
1. Expecting to match text nodes end with ':'

E.g., <p>Value:</p>

What version of the product are you using? On what operating system?
Windows 7

Please provide any additional information below.

I understand Firepath currently supports XPATH1.0 expressions. Any suggestions 
are welcome to enhance this add-on to work with XPATH2.0 expressions.

Expecting Your help urgently as we are blocked by our new requirement.

Thanks,
Prabakaran

Original issue reported on code.google.com by pappu.s...@gmail.com on 6 Jan 2013 at 1:06

@GoogleCodeExporter
Copy link
Author

Issue 40 has been merged into this issue.

Original comment by pierre.t...@gmail.com on 9 Jun 2013 at 11:39

@GoogleCodeExporter
Copy link
Author

Hi, similarly functions like fn:matches are only supported in XPATH 2.0
It would be great if firepath is upgraded to 2.0 engine.

Thanks,
praneel

Original comment by praneel....@gmail.com on 21 Oct 2013 at 12:07

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

No branches or pull requests

1 participant